BBS Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ BBS Toolkit / BBS Toolkit.iso / programs / pb121.zip / PB121.DOC < prev next >

Wrap

Text File | 1992-03-28 | 257KB | 7,094 lines

██████ ██████ ███ ██ ██ ██ ██ ██ ██ ██ ██ ███ ████ ██ ██ ████ ████ ██ ███ ██ █████ ███ ██ ██ ██ █████ ██ ██ ██ ███ ██ █████ ██ ██ ██ ██ ██ ██ ██ ██ ██ █████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ████ ████ ████ ██████ ████ ██████ ████ ██████ Version 1.21 March 28, 1992 Copyright (c) 1990-1992 Philippe Leybaert All rights reserved ────────────────────────────────────────────────────────────────── The following names/products mentioned in this documentation are copyrighted material, trademarks or registered trademarks: Bimodem Erik Labs BNU David Nugent/Unique Computing Pty Ltd. Borland C++, Turbo C++ Borland International, Inc DESQview Quarterdeck Office Systems DoorWay Marshall Dudley DR DOS Digital Research EFL (Enhanced File List) Paul Tabara FidoNet Tom Jennings IBM PC/XT/AT International Business Machines, Inc MBUTIL Gerard van der Land MS-DOS , Microsoft C Microsoft, Inc Multi-Edit American Cybernetics, Inc Opus Wynn Wagner III QuickBBS & QEcho The QuickBBS Group, Inc QuickEd Tirosh Bros. RemoteAccess (RA) Continental Software, Inc TLIB Burton Systems Software TosScan & FrontDoor Joaquim H. Homrighausen Turbo Assembler/Debugger Borland International, Inc X00 Ray Gwinn ZmailH Claude N. Warren Zortech C++, BLink Zortech, Inc GECHO Gerard J. van der Land ────────────────────────────────────────────────────────────────── - 1 - ╒══════════════════════════════════════════════════════════════════╕ │░░░░░░ IMPORTANT INFORMATION - READ THIS FIRST ░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════════╛ - ProBoard (all executables and documentation files) is copyrighted material of Philippe Leybaert. - You can use ProBoard for a period of 30 days, free of charge. If you use the software after the evaluation period, you MUST register. (For registration information, see the appropriate section of this manual) - After registration, you are allowed to use ProBoard for as long as you like, and your registration is valid for all future versions up to, but not including v2.00. You will probably receive a free upgrade to v2.00, but we do not guarantee this. - We reserve the right to quit giving support or releasing updates of the software. - The software and other materials included in the distribution archive are provided "AS IS" without warranty of any kind. We do not guarantee the correct functioning and/or reliability of the software. The authors will not be liable for any direct or indirect damages, resulting from the use of the software. - You may not reverse-engineer ProBoard in any way and you may not add, change or delete any files in the distribution archive. - You are free to distribute the original, unmodified ProBoard archive provided no fee is charged for its distribution. This excludes charges for online time on electronic bulletin boards or other communication services. - EFL.PEX, EFLCFG.EXE, and related files are copyrighted material of Paul Tabara. - 2 - ╒══════════════════════════════════════════════════════════════════╕ │░░░░░░ CONTENTS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════════╛ INTRODUCTION .................................... 5 - Description .............................. 5 - Features ................................. 6 - Support .................................. 6 - Technical Info ........................... 8 - Credits .................................. 8 REGISTRATION .................................... 10 INSTALLATION .................................... 13 - First Time Installation .................. 15 - RemoteAccess to ProBoard ................. 17 - QuickBBS to ProBoard ..................... 19 CONFIGURATION ................................... 20 - Options (F1) ............................. 20 - Protocols (F2) ........................... 27 - Message areas (F3) ....................... 31 - File areas (F4) .......................... 34 - Time/download limits (F5) ................ 36 - User Editor (F6) ......................... 37 - Menu Editor (F7) ......................... 40 - Matrix Addresses (F8) .................... 41 - Modem Parameters (F9) .................... 41 - Events (Shift-F1) ........................ 44 - Personal Files (Shift-F2) ................ 45 - Edit Statistics (Shift-F3) ............... 46 SECURITY ........................................ 47 - Levels & Flags ........................... 47 - Trashcan ................................. 47 MENUS ........................................... 48 - Setting up menus ......................... 48 - Menu Security ............................ 49 - Creating menus ........................... 50 - Hints .................................... 52 - Menu Function Summary .................... 53 - Menu Function Overview ................... 55 USERS ........................................... 90 - Loglevels ................................ 90 - 3 - ECHOMAIL & NETMAIL .............................. 91 - Echomail ................................. 91 - Netmail .................................. 91 PBUTIL .......................................... 93 - Message Packer ........................... 94 - Message Indexer .......................... 94 - Message Linker ........................... 94 - User File Packer ......................... 95 - User File Indexer ........................ 95 - User File Fixer .......................... 95 - User Killer .............................. 96 - File Counters ............................ 97 - Nodelist Compiler ........................ 97 - Music Player ............................. 99 REFERENCE ....................................... 100 - Multi-user operation ..................... 100 - Sysop keys ............................... 101 - Command line options & errorlevels ....... 104 - AVATAR/0 and AVATAR/0+ ................... 107 - Hard-coded .A?? files .................... 108 - .A?? file control codes .................. 110 - Music Files .............................. 113 - Text Macros .............................. 114 - Example batch files ...................... 117 - Flag Cross-Reference Chart ............... 120 - FREE Files ............................... 121 USER'S GUIDE TO PROBOARD ........................ 122 - Navigating through menus ................. 122 - The More Prompt .......................... 123 - The [S] & [P] keys ....................... 123 - Standard Chatting Procedure .............. 123 SOFTWARE DEVELOPMENT KIT ........................ 124 ENHANCED FILE LIST (EFL) PEX FILE ............... 125 - Installation ............................. 125 - FrontDoor Notes, High Speed Modems ....... 126 - 4 - ╒══════════════════════════════════════════════════════════════════╕ │░░░░░ INTRODUCTION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │ ╘══════════════════════════════════════════════════════════════════╛ ┌──────────────────────────────────────────────────────────────────┐ │ Description │ └──────────────────────────────────────────────────────────────────┘ ProBoard is a program that allows you to run a public or private BBS. A BBS is a Bulletin Board, where files, messages and other useful things may be exchanged between users. The operator of a BBS is called the System Operator, or SysOp. He/she is responsible for the correct functioning of the BBS. Therefore, this manual is primarily intended for Sysops, or future Sysops. ProBoard has everything you need to efficiently run a BBS, and more. It's even possible to use ProBoard within a mail network. Furthermore, more than one user at a time can use a BBS running ProBoard, by making use of a network or multitasker like DESQview. The greatest asset of ProBoard is that it has most of the features (and much MORE!) of QuickBBS and RemoteAccess, yet needs a small amount of memory and disk storage space to run. You could run three copies of ProBoard on just one PC using Desqview. On a 80386 computer with 4MB of RAM, you could run 4 nodes, and still have a 600K DOS window at your disposal! When running an external program, ProBoard can swap itself to disk/EMS, and stay resident in only 2000 bytes !!! The most important feature is undoubtedly the ability to extend ProBoard by writing your own extensions in C or C++. ProBoard uses RA/QuickBBS compatible message base files and user files. All known utilities for RA v1.11 will work with this version of ProBoard. - 5 - ┌──────────────────────────────────────────────────────────────────┐ │ Features │ └──────────────────────────────────────────────────────────────────┘ This is a list of the most important features not found in other BBS software: - A software development kit! Write your own extensions to ProBoard using C or C++. You can write "internal doors", and a lot more!! THIS IS UNIQUE!! - Swaps itself to disk or EMS , leaving only 2 (two) Kb resident! - Extremely flexible protection against excessive downloaders. - REAL-TIME multi-line chat built in. No stupid line-per-line chat. - Advanced CD-ROM support. The CD-ROM drive is not accessed until a file is actually downloaded. - VERY flexible protocol configuration. You can install all protocols directly in ProBoard, including Zmodem,Xmodem,Puma, Lynx, Bimodem (FULL support!),... - Files can be downloaded from all areas at once, a single area or from ANY combination of areas. - You can set download-limits per file area (# files & # Kb) - More control over the control codes in textfiles: left/right aligned, fixed field length,... - Sysop macros: you can assign keystrokes to function keys! - Extremely fast!! - IBM-specific characters can be filtered out for certain users. - Personal files: users can exchange private files! - Expiration dates. Let ProBoard lower a user's level at a given date. - Advanced support for extended text modes (132 columns) - Extremely user-friendly configuration/maintenance. - Unlimited customization - Runs doors created for several major BBS packages, including RemoteAccess (RA), QuickBBS, PC Board, and others. ┌──────────────────────────────────────────────────────────────────┐ │ Support │ └──────────────────────────────────────────────────────────────────┘ For problems, bug-reports, etc. please write to: Philippe Leybaert ProBoard USA BBS Groenplein 15 Mike Wagner B-9060 Zelzate P.O. Box 111 BELGIUM Chaska, MN 55318 USA - 6 - Or you can fax to the following number: +32-91-444-938 You can also reach the authors by sending E-mail: - Philippe Leybaert : FidoNet (2:292/1905.1) CompuServe (70314,2021) - Rutger Lasuy : FidoNet (2:292/1905) If you have any questions or comments, or you need utilities for ProBoard, call one of the support boards: - ProBoard USA BBS (Fido 1:282/109) Sysop: Mike Wagner Hours: 24/24 Speed: 1200-14400 (v.32bis/v.42bis) Tel : (612) 368-4703 - ProBoard Support Benelux (Fido 2:292/1900) Sysop: Marc Van Loocke Hours: 24/24 Speed: 1200-9600 (v.32/MNP) Tel : +32-91-202-531 - The Home of ProBoard (Fido 2:292/1905) Sysop: Rutger Lasuy Hours: 24/24 Speed: 1200-14400 (v.32bis/v.42bis) Tel : +32-91-66-22-91 There is an international FidoNet ProBoard Support echo available. Be sure to ask your Net Coordinator about it. The name of the echo is "PROBOARD". Although we try very hard, due to the volume of support requests we receive from registered users, we can only offer limited support to non-registered users. For the latest version of ProBoard and utilities, you can call one of the support boards (above), or: - The O-Zone BBS (Fido 1:282/30) Sysop: Jim Biggs Hours: 24/24 Speed: 1200-14400 (HST/v32bis/v42bis) Tel : (612) 591-7767 - 7 - - Rivendell BBS (Fido 1:282/90) Sysop: Paul Tabara Hours: 24/24 Speed: 1200-14400 (HST/v32bis/v42bis) Tel : (612) 323-9473 ProBoard is also available on CompuServe (IBMBBS forum). ┌───────────────────────────────────────────────────────────────────┐ │ Technical Info │ └───────────────────────────────────────────────────────────────────┘ ProBoard is entirely written in C++ and Assembler. No third-party libraries are used, so we have TOTAL control over the code! For the development of ProBoard, we used the following tools: Compiler......... Borland C++ v3.0 Linker........... TLink, part of Borland C++ v3.0 Assembler........ Turbo Assembler v3.0 Debugger......... Turbo Debugger v3.0 Editor........... Multi-Edit Professional 5.01 Version Control.. TLIB v4.12f ┌───────────────────────────────────────────────────────────────────┐ │ Credits │ └───────────────────────────────────────────────────────────────────┘ ProBoard and all the included utilities are written by: Philippe Leybaert and Rutger Lasuy Documentation: Original text : Rutger Lasuy English translation : Jim Biggs &1.21 additions Paul Tabara Mike Wagner Final editing : Philippe Leybaert - 8 - Beta-testing: ──────────────── ────────────────────────── ─────────────── Sysop System FidoNet Address ──────────────── ────────────────────────── ─────────────── Nolden Thrift The Thrift Shop 1:151/803 Richard Vonzel The File Cabinet BBS 1:282/27 Jim Biggs The O-Zone BBS 1:282/30 Craig Peterson FlightLine BBS 1:282/47 Tom Krueger The Senate Chamber 1:282/56 Paul Tabara Rivendell BBS 1:282/90 Mike Wagner Milling A Round 1:282/109 Greg Shaffer Route 66 BBS 1:370/510 Ed Ivey Ed's Place 1:3616/1 Andy Smith The Business Connection 1:3645/10 Johan Widingsjo Flash Gordon 2:201/415 Steven Debruyn Magic BBS 2:292/1201 Tim De Meyer MultiNet Home Base 2:292/1400 Marc Van Loocke ProBoard Support Benelux 2:292/1900 Koen Weytens Line Up II 2:292/1904 Patrick Thijs Connect BBS 2:294/40 Allan Soreyn Electro-Line BBS 2:296/120 Alain Luckx Computron BBS (n/a) Eddy Impens F-Three BBS (n/a) - 9 - ╒══════════════════════════════════════════════════════════════════╕ │░░░░░░ REGISTRATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │ ╘══════════════════════════════════════════════════════════════════╛ ProBoard is SHAREWARE. This means that you are granted a 30-day evaluation period, after which you must register. You will receive a registration key file through netmail or it will be uploaded to your BBS if you don't have a FidoNet node number. If none of this is possible, please indicate this on your registration form, along with what size diskette you need and we will mail you your key on a diskette. Arrangements can also be made for you to download your key from the ProBoard USA support BBS. The key file is valid for all future versions of ProBoard up to 2.00. Registration fees for non-commercial use are as follows: USA................. 40 US$ Canada.............. 50 CAN$ Belgium............. 1500 BF The Netherlands..... 85 FL UK.................. 25 BP Germany............. 75 DM France.............. 275 FF When you use ProBoard in a commercial environment, multiply the registration-prices by 5. Commercial registrations include the printed & bound ProBoard manual and free support by fax/bbs. To register, print the registration form on the next page, fill it out, and send it together with your payment (check or money order) to the following address: For the US and Canada: ProBoard USA c/o Mike Wagner P.O Box 111 Chaska, MN 55318 USA In the United States and Canada, make checks payable to ProBoard USA. (US Currency only!) - 10 - For Europe: (Use a "EuroCheque" for your registration!) Rutger Lasuy Krakeelstraat 5 B-9260 Serskamp BELGIUM If you live in Belgium, you can transfer the registration amount (1500 BF) to our account number: 449-2774401-84. - 11 - ------------------------------------------------------------------ ProBoard version 1.21 ---- Registration Form ------------------------------------------------------------------ Your Name : _____________________________________________ Company : _____________________________________________ Sysop Name : _____________________________________________ BBS name : _____________________________________________ Note: if we can not deliver your key via FidoNet, or a call to your BBS, please indicate which diskette size you prefer below and a key file will be mailed to you. Diskette-size: ( ) - 5"1/4 ( ) - 3"1/2 (check one) Address : _____________________________________________ _____________________________________________ _____________________________________________ Primary BBS phone number : __________________________________ Hours of operation : __________________________________ Is your system part of FidoNet? ( ) - Yes ( ) - No If so, what is your network address? _______________________ Type of registration: ( ) - Personal ( ) - Commercial Registration amount enclosed: _______________________________ What would you like to see added or changed in future versions? _____________________________________________________________ _____________________________________________________________ _____________________________________________________________ _____________________________________________________________ - 12 - ╒══════════════════════════════════════════════════════════════════╕ │░░░░░░ INSTALLATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════════╛ If you currently operate either a RemoteAccess or QuickBBS bulletin board system, continue reading this chapter for specific instructions on how to convert your existing system to ProBoard. The system-requirements for ProBoard are: - DOS v3.10 or higher - 350 Kb of free system memory (180 Kb for the overlayed version of PROBOARD.EXE) - A FOSSIL driver (eg. X00 or BNU) A FOSSIL driver can be obtained from many BBS's (including from the ProBoard Support BBS). The following guidelines are intended for a single-user system. Please refer to the appropriate section on how to install a multi-user system. ProBoard is distributed in a compressed file (PB_121.ARJ). Make the following subdirectory for ProBoard to be installed in. C:\PB (the main ProBoard directory) Unzip PB_121.ARJ in C:\PB in order to obtain the following files: PROBOARD.EXE ProBoard executable PROCFG.EXE ProBoard configuration program PBUTIL.EXE Maintenance utility PB121.DOC This file PB121SDK.DOC Documentation on the ProBoard SDK P.BAT Basic batch file EX_MNU.ARJ Example menus EX_TXT.ARJ Example ANS/ASC files EX_CFG.ARJ Example configuration files CONVERT.EXE Conversion utility SDK.ARJ ProBoard Software Development Kit (PEX) EFL121.ARJ Enhanced File List (EFL) Sample PEX File Now, you need to create the following subdirectories. - 13 - C:\PB\MENUS (where your menus will be stored) C:\PB\TXTFILES (for the text files that ProBoard will use) C:\PB\MSGBASE (where your messages will be stored) C:\PB\PEX (where ProBoard Executable (PEX) files are stored) C:\PB\PVTFILES (where "Private" files to/from users are placed) C:\PB\ULOADS (where files users upload will be placed) C:\PB\DLOADS (where files users can download will be kept.) With previous versions of ProBoard (1.0x), you had to set 2 environment variables (PROBOARD and DSZLOG). This is not necessary with this version. ProBoard looks for its data files in the directory where PROBOARD.EXE is located. You can, however, tell ProBoard to look for the data files in another directory by setting the environment variable PROBOARD (eg. SET PROBOARD=F:\PB). The environment variable DSZLOG used by most protocols is not needed. ProBoard will set this variable prior to starting the protocol. ProBoard is now ready to be configured by ProCFG. This is discussed in the next chapter titled "Configuration". Once ProBoard is installed, you should start it with a batch file. ProBoard should ALWAYS be run with a batch file, because it returns to DOS when a user logs off. Below is a basic batch file for stand-alone operation (without a mailer). It is called P.BAT and is included in PB_121.ARJ :again PROBOARD -S if errorlevel 99 goto out if errorlevel 1 goto fatal goto again :fatal echo A fatal error occured. goto x :out echo Normal exit. :x Note that errorlevels 2-4 generate a fatal error. These error- levels are used for mail networking, and ProBoard should not return one of these errorlevels in a standalone environment. The PROBOARD.EXE command line options are discussed in the "Reference" chapter later in this manual. - 14 - ┌──────────────────────────────────────────────────────────────────┐ │ First-Time Installation │ └──────────────────────────────────────────────────────────────────┘ Most people want to unpack the ProBoard files, and want to see something working right away. This section explains what to do to get your system up and running quickly. We will assume that you created (see above) the directory C:\PB as ProBoard's main system directory. 1. Create the following directories: C:\PB\MENUS C:\PB\TXTFILES C:\PB\PEX C:\PB\MSGBASE 2. Unpack ProBoard in the directory C:\PB 3. Unpack the file EX_TXT.ARJ in the directory C:\PB\TXTFILES 4. Unpack the file EX_MNU.ARJ in the directory C:\PB\MENUS 5. Unpack the file SDK.ARJ in the directory C:\PB\PEX 6. Unpack the file EX_CFG.ARJ in the directory C:\PB 7. Run ProCFG and enter the correct modem parameters for your modem (explained in the next chapter, "Configuration") After these seven steps you can run ProBoard, but you will not be able to use the fullscreen editor or perform file transfers. To log in locally, you execute PROBOARD.EXE without parameters. To make ProBoard answer incoming calls, run PROBOARD -S. 8. Run ProCFG and create some file and message areas. (explained in the next chapter, "Configuration") 9. Download QuickED from a BBS, copy it in the directory C:\PB and run the QuickED configuration program. (QuickED can be found on any ProBoard Support BBS) - 15 - 10. Download DSZ from a BBS and copy the file DSZ.COM or DSZ.EXE in the directory C:\PB. (DSZ can be found on any ProBoard Support BBS) Now, you will be able to run ProBoard, use the fullscreen editor, and allow users to perform file transfers using X,Y & Zmodem. - 16 - ┌──────────────────────────────────────────────────────────────────┐ │ RemoteAccess to ProBoard Conversion │ └──────────────────────────────────────────────────────────────────┘ If you are operating a RemoteAccess system, you can convert your existing userfile, message files, message areas, file areas and menus to the format used by ProBoard. This is done by running CONVERT.EXE in the ProBoard system directory. But, before you do ANYTHING, we highly recommend that you back up your existing files. Here's the procedure to follow: - Backup your existing files. - Install ProBoard as explained earlier (don't forget to setup and create all directories needed by ProBoard) - Move to the ProBoard system directory (usually C:\PB). - Copy the following files from your RA message base directory to the ProBoard message base directory: USERS.BBS, USERSXI.BBS, LASTREAD.BBS, MSGINFO.BBS, MSGHDR.BBS, MSGTXT.BBS, MSGIDX.BBS, MSGTOIDX.BBS. - Run CONVERT RA <ra-dir> eg. CONVERT RA C:\RA - Run PBUTIL with the UF parameter. eg. PBUTIL UF Things you will have to do manually: - Enter all system parameters in ProCFG (like paths). - Enter the user levels & download limits in ProCFG - Check all file- and message-related functions for the correct data fields. ProBoard uses a different (more advanced) method for specifying areas. - Enter any events you have in PROCFG. - Copy any .Q-A files to the ProBoard directory. - If you had a "Message to Sysop" /T=User_Name in RA, find that entry in your new ProBoard menu. Change it to /T="User Name" (Note: NO UNDERSCORE!!) ┌──────────────────────────────────────────────────────────────────┐ │ RA Compatible Files │ └──────────────────────────────────────────────────────────────────┘ ProBoard uses different files than RA to store the file area and message area configurations. Therefore, to run any of your RA-utilities that use the files CONFIG.RA, FILES.RA, MESSAGES.RA, TIMELOG.BBS and SYSINFO.BBS, you must first run a conversion. - 17 - Use the CONVERT utility (Supplied with PB_121.ARJ) to create these files from the ProBoard system files. Run 'CONVERT SIMUL' in the ProBoard system directory to create the following files: CONFIG.RA FILES.RA MESSAGES.RA TIMELOG.BBS SYSINFO.BBS You must run this conversion before you attempt to use your favorite RA utilities. This needs to be done only once initally, and then thereafter only when you have made changes to ProBoard using PROCFG.EXE. You do not need to run 'CONVERT SIMUL' each time you run one of your RA utilities. - 18 - ┌──────────────────────────────────────────────────────────────────┐ │ QuickBBS to ProBoard Conversion │ └──────────────────────────────────────────────────────────────────┘ If you are operating a QuickBBS system, you can convert your existing userfile, message files, message areas, file areas and menus to the format used by ProBoard. This is done by running CONVERT.EXE in the ProBoard system directory. But before you do ANYTHING, we highly recommend that you back up your existing files. Here's the procedure to follow: - Backup your existing files. - Install ProBoard as explained earlier (don't forget to setup and create all directories needed by ProBoard) - Move to the ProBoard system directory (usually C:\PB). - Copy the following files from your QBBS message base directory to the ProBoard message base directory: USERS.BBS, LASTREAD.BBS, MSGINFO.BBS, MSGHDR.BBS, MSGTXT.BBS, MSGIDX.BBS and MSGTOIDX.BBS. - Run CONVERT QBBS <QBBS-dir> eg. CONVERT QBBS C:\QUICKBBS - Run PBUTIL with the UF parameter. eg. PBUTIL UF Things you will have to do manually: - Enter all system parameters in ProCFG (like paths). - Enter the user levels & download limits in ProCFG - Check all file- and message-related functions for the correct data fields. ProBoard uses a different (more advanced) method for specifying areas. - Enter the events you have in PROCFG. - Copy any .Q-A files to the ProBoard directory. - If you had a "Message to Sysop" /T=User_Name in QBBS, find that entry in your new ProBoard menu. Change it to /T="User Name" (Note: NO UNDERSCORE!!) - 19 - ╒══════════════════════════════════════════════════════════════════╕ │░░░░░░ CONFIGURATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════════╛ ProBoard is completely configured by PROCFG.EXE. This program can be executed from any directory. In most of the menus, just press <Ins> to add an item, press <Del> to remove an item, and press <Enter> to select an item. ┌──────────────────────────────────────────────────────────────────┐ │ Options (F1) │ └──────────────────────────────────────────────────────────────────┘ This is the first option to choose when running PROCFG.EXE. A second menu will be displayed with the following items: - Paths - New Users - Security - Yelling - System Options - File Transfer - Display Options - Text Strings - Site Info A description of these fields follows. ┌──────────────────────────────────────────────────────────────────┐ │ Paths │ └──────────────────────────────────────────────────────────────────┘ Textfiles ................... Directory where ProBoard's textfiles are stored (drive included!). Menus ....................... Directory where ProBoard's menus are stored (drive included!). Message Base ................ Directory where the message base will be stored (drive included!). Uploads ..................... Directory where the users' uploads will be stored (drive included!). - 20 - Private Uploads ............. Directory where personal files are stored. (for file exchanges between users). Nodelist Directory .......... Directory where the nodelist is located. For use by the nodelist compiler. Leave this field blank if you do not have a nodelist. PEX Files ................... Directory where the PEX files should be stored. Editor Command .............. The external editor's filename and path (eg. C:\PB\QUICKED.EXE). You can also use shell options here (refer to menu type 7 for more info). Example: *SQUICKED.EXE If you are not using an external editor, leave this field blank and ProBoard will default to it's internal editor. ┌──────────────────────────────────────────────────────────────────┐ │ New Users │ └──────────────────────────────────────────────────────────────────┘ New User Level .............. The level a user will have upon his or her first login. New User Flags .............. The flags a user will have upon his or her first login. New User Loglevel ........... The loglevel a user will have upon his or her first login (more info about this later). Allow ANSI .................. Allows New Users to select ANSI terminal emulation. Allow AVATAR ................ Allow new users to select either AVATAR/0 or AVATAR/0+ terminal emulation. Ask Phone Number ............ Determines whether ProBoard should ask for a user's phone number upon his/her first login. - 21 - ┌──────────────────────────────────────────────────────────────────┐ │ Security │ └──────────────────────────────────────────────────────────────────┘ Allow Quick Login ........... If this is enabled, the Sysop can login as Sysop by pressing [Enter] at the login prompt without entering a password. If you don't like this, just turn it off. Write Pwd-Failure Messages .. If a user fails to log in because he/she exceeded the maximum number of password retries, ProBoard can write a security message to that person and to the Sysop, telling him/her what happened. This can be turned on or off with this option. Allow Login With Alias ...... Determines if ProBoard will allow users to login with their alias (handle). Users can also select or change their alias using Menu Function 59. If this option is set to "No", ProBoard will not ask new users to select an alias. Log Local Calls ............. If this option is enabled, all local logins will be logged in the file PROBOARD.LOG (ProBoard's system log). Hide Sysop Activity ......... If enabled, ProBoard will hide all Sysop activity from the Last Callers list (Function 51), Show Users Online (Function 50), and from the display of the User List (Function 13). Max. Password Retries ....... Maximum number of incorrect password attempts ProBoard will allow, before logging the user off. Min. Password Length ........ The minimum length of a password. Security Message Area ....... The message area number where ProBoard's Security Manager should write it's security related messages. Level For Crashmail ......... Level needed to send crashmail. Flags For Crashmail ......... Flags needed to send crashmail. - 22 - Level For Fileattach ........ Level needed to do a file attach for Netmail. Flags For Fileattach ........ Flags needed to do a file attach for Netmail. Use System Password ......... (Yes/No). If set to "Yes", ProBoard will require all incoming callers to know and enter a 'System Password' before asking them for their user name and user password. Great for running a 'Private' BBS in a corporation, etc. If set to "No" users will not be prompted for a 'System Password'. System Password ............ If the above option 'Use System Password' is set to 'Yes', this is the password users are required to enter to gain access to the BBS. Users who fail logging in (perhaps they forgot or do not know the system password), will be allowed to enter a message to the SysOp explaining their situation, after which, ProBoard will log the user off. ┌──────────────────────────────────────────────────────────────────┐ │ Yelling │ └──────────────────────────────────────────────────────────────────┘ Max. Sysop Pages ............ Number of times a user can page the Sysop during one session. PageBell Length ............. Number of seconds the Sysop paging bell will ring. Page Start Time ............. Users can only yell during these Page End Time ............... hours (in 24 hour format). - 23 - ┌──────────────────────────────────────────────────────────────────┐ │ System Options │ └──────────────────────────────────────────────────────────────────┘ Check Mail At Login ......... Determines whether ProBoard should check for new mail and files upon login. If set to "Ask", ProBoard will ask the user if they want to check for waiting mail/personal files. Allow One-Word Names ........ Determines whether a user's name can be a single word. Date Format ................. Determines if ProBoard should display all dates in European format (DD/MM/YY) or American format (MM/DD/YY). Use File Sharing ............ Set this option to "Yes", if you want to share the message base with FrontDoor or any other utility that uses the same locking scheme as RemoteAccess 1.10 / FrontDoor 2.02 Swap to Disk ................ Determines the default shelling mode. If this option is set to ON, ProBoard will be swapped to disk/EMS, leaving only 2000 bytes resident! Fast Mode ................... When this option is enabled, ProBoard will use about 10Kb more memory (depending on the number of file-areas), but the system will run faster. Kill Netmail When Sent ...... Controls whether netmail will be killed after a message has been exported from the messagebase. Inactivity Limit ............ Number of seconds a user is allowed to remain idle. If the user hasn't typed anything when this limit is exceeded, they will be logged off. Quote String ................ This string is used to when ProBoard quotes a message for a reply. A '@' character is replaced by the initials of the user who wrote the message quoted from. - 24 - Password Display ............ Enter the character that you want ProBoard to display to users, as they enter their password. # Usage Graph Days .......... Enter the number of days you would like to have displayed on your system usage graphs. ┌──────────────────────────────────────────────────────────────────┐ │ File Transfer │ └──────────────────────────────────────────────────────────────────┘ Minimum Upload Space ........ Space needed on the upload drive for uploads to be allowed. Download Start Time ......... The time that users can begin downloading files (Except when the "Ignore DL" flag is set in the user's record). Download End Time ........... The time after which downloads can not be performed (except when the "Ignore DL" flag is set in the users record). ┌──────────────────────────────────────────────────────────────────┐ │ Display Options │ └──────────────────────────────────────────────────────────────────┘ Use 43/50 Line Mode ......... Enable local display of ProBoard in 43 or 50 line mode. Show User Info Window ....... Should ProBoard display the User Info Window, when users are online. ┌──────────────────────────────────────────────────────────────────┐ │ Text Strings │ └──────────────────────────────────────────────────────────────────┘ Start Chat .................. displayed to the user when you press <ALT-C> to enter into chat mode. - 25 - End Chat .................... displayed to user when you press <ESC> to end chat mode. Scanning User File .......... displayed to user during login, after user has been asked for their name, but before they are asked for their password. Editing User Record ......... displayed to a user who is online, when you press <ALT-E> to invoke the user editor to edit their user record. Sysop DOS Shell ............. displayed to user who is online, when you press <ALT-J> to jump (shell) to DOS. Returned From DOS ........... displayed to user when you type the DOS "EXIT" command to return to the BBS, after jumping/shelling to DOS. Shelling .................... displayed to the user when an external program is run. Checking for mail ........... displayed to the user when they check to see if they have any mail waiting. No mail found ............... displayed to the user after ProBoard has checked for waiting mail, but none was found. You can insert text macros in any of these text strings. Also, a '|' (pipe symbol) will be replaced by a CR/LF. (Return/Linefeed) ┌──────────────────────────────────────────────────────────────────┐ │ Site Info │ └──────────────────────────────────────────────────────────────────┘ System Name ................. The name of your BBS. Will be written to EXITINFO.BBS. Be sure this matches any "keys" you might have for any door programs. Sysop Name .................. The name of the Sysop. This also will be written to EXITINFO.BBS - 26 - Default Origin Line ......... Default origin line, used for Echomail (more about this later). Number of Nodes ............. Used for multi-line systems. Enter the maximum number of users allowed to log in at the same time (max. 255) ┌──────────────────────────────────────────────────────────────────┐ │ Protocol Configuration - (F2) │ └──────────────────────────────────────────────────────────────────┘ The second (POWERFUL) option in PROCFG.EXE is 'Protocols'. You may want to skip this option when doing a first-time installation of ProBoard, as many protocol configurations are included in the file PROTOCOL.PRO. You should select each protocol listed and set 'Enabled' to 'No' (you won't lose the protocol configuration) unless you have the actual protocol file itself physically on your hard drive. The protocols themselves are NOT included with ProBoard, but can be obtained from any ProBoard Support BBS, as well as many others. Downloading and uploading files has always been one of the most important activities of BBS's. Most BBS programs have file transfer protocols pre-installed and do not allow additional protocols to be configured. ProBoard's philosophy is entirely different: no protocols are actually embedded in the code, all protocols are external and are being called by ProBoard. As of yet, we don't know of any external protocol incompatible with ProBoard, Bimodem included! If you happen to find one that you think is an incompatible external file transfer protocol, please let us know! Upon selection of the 'Protocols' option, a submenu is displayed containing the protocols already present. Add a protocol by pressing <Ins>, remove a protocol by pressing <Del>. A protocol is entirely defined by the following parameters: Protocol Name ............... Protocol's name, to be displayed in the down/upload menu. This can include a short description if you like. Hotkey ...................... Key to be pressed by the user to activate the protocol. - 27 - Batch ....................... Determines whether the protocol can handle batch-mode (whether it can handle multiple files). Xmodem for example can handle only one file at a time, while Zmodem can handle multiple files. Enabled ..................... ProBoard comes with several pre- configured protocols for which you may not have the necessary files. It would be useless to have these protocols displayed in the menu. You can prevent this by setting Enable to 'No', without having to lose the configuration for this protocol. Both-Way .................... Determines whether the protocol is a full-duplex protocol, ie. whether it can send and receive files at the same time. (eg. Bimodem) Bimodem ..................... The Bimodem protocol uses an odd format for its control file. Setting Bimodem to 'Yes' causes the control file to be written to disk in Bimodem-format. Log File .................... Name of the log file created by the protocol. After the file transfer, the information needed to update the user-records will be obtained from this file by ProBoard. Most protocols write a file specified in the environment variable DSZLOG. ProBoard will set this variable to the right filename for you. ProBoard checks for the logfile in the directory where it was started from, so if some external protocol writes a different logfile than the one specified in the DSZLOG-variable, make sure it writes the file in the startup-directory! - 28 - Control File ................ Protocols that can handle batch-mode usually allow parameters to be passed not only on the command line, but also (should the command line grow too long) by means of a control file. ProBoard must know of this file, to be able to pass the file- names to the protocol. Download Command ............ Command needed to start the protocol in download-mode. You may want to use the shell options of menu function 7 here. If the first character of this command is a '@', the named pex-file will be run. Note that no shell parameters (*x) are supported when calling a pex-file. You can use string macros though. IMPORTANT: The command should be in- dependent of the path it is called from. Batch-mode protocols also require a control file to be specified. Should you, anywhere in this field, fill in a '#', then this character will at run-time be replaced by the filename of the file to be sent (only for non-batch protocols). Upload Command .............. Command needed to start the protocol in upload-mode. Here also, the command should be independent of the directory it is called from and a '#' will be replaced by the filename of the file to be received (for non-batch protocols), or by the directory where files should be received into (for batch-protocols). A '@' as the first character will execute a pex-file (see DL Command). - 29 - Download String ............. Determines what should be written in the control file when downloading. A '#' character is replaced by the path and filename of the file to be sent to the user. Most often, a single '#' is the only character in this field. This works for most of the protocols. Example: In case a user wants to download 3 files, entering 'Send #' in this field causes the following to be written in the control file: Send C:\PB\FILES\COMM\TM.ARJ Send C:\PB\FILES\COMM\TBILL.ARJ Send C:\PB\FILES\UTIL\SHEZ55.ARJ You can always take a look at the pre-configured protocols, to lighten things up for you. Upload String ............... <reserved for future use> Download Keyword ............ In order to allow ProBoard to update the user-records from the protocol's log file, a keyword must be specified to indicate a file has successfully been sent. If a protocol writes 'Sent <filename>' in the logfile, you should specify 'Sent' as the keyword. This keyword is CASE SENSITIVE! Upload Keyword .............. Same as the previous field, for uploads. - 30 - File Word Number............. This is the number of the sent file's filename, counting from the keyword, but NOT including the keyword. This is used for both uploads and downloads. Eg. Sent 12/05/90 12334 PB_100.ARJ In this case, you should enter '3' as the word number, because PB_100.ARJ is the third word counting from, but not including, the keyword ('Sent'). Efficiency .................. A percentage that gives the throughput efficiency for this protocol. This value is used to estimate the time needed to perform a file transfer. CONCLUSION: Correctly installing the protocols may seem somewhat difficult at first, but you will soon get used to it. And don't forget that the most popular protocols are already pre-configured in ProBoard! ┌──────────────────────────────────────────────────────────────────┐ │ Message Areas - (F3) │ └──────────────────────────────────────────────────────────────────┘ ProBoard can have up to 200 different message areas. Each message area has its own name and properties. For example, you could have message areas for public messages only, message areas for Echomail, or an area to create "Announcements" for your users. You can configure all of this with the ProBoard message area editor. Selecting 'Message Areas' from the Main Menu, gives you a list of the available areas (which initially is empty of course,). You edit a Message Area by pressing [Enter]. The ProBoard message base is capable of holding approx. 32,000 messages. However, due to the limitations of the Hudson style message base, you should not let your message base exceed 16 megabytes in size. - 31 - A message area has the following fields: Name ........................ Name of this message area. Message kind ................ The kind of message. You can have: - Local Local messages - EchoMail Echomail - NetMail Netmail - Pvt EchoMail Private Echomail One word about the difference between the "Echo" type and the "Pvt Echo" type: In "Echo" areas, it is not allowed to delete messages that have been exported by an echomail processor (as specified by the FTSC, the FidoNet Technical Standards Committee). In a "Pvt Echo" area, this restriction is not imposed. Message Type ................ One of the following: - Private only Only private messages allowed. - Pvt/Public Private or public messages allowed. - Public only Only public messages allowed. - To All This message type should be used in a LOCAL message area only. It is intended for a Sysop to leave messages to all users. Any messages entered in this area will considered "To All" regardless of the whom the "To" is addressed to. Messages entered in this area will be shown when ProBoard checks for waiting mail. You should not allow users to reply to these messages since their replies will be sent to all users. Instead, set the reply area to a different area. - 32 - Name Options ................ Determines which names can be used to write messages in this area. This can be: - Real Names Only - Free Alias - Fixed Alias It is recommended that areas where aliases are allowed, are made "Public Only". Read Level .................. Level needed to read messages in this area. Read Flags .................. Flags needed to read messages in this area. Write Level ................. Level needed to write messages in this area. Write Flags ................. Flags needed to write messages in this area. Sysop Level ................. Level needed to be allowed EVERYTHING in this message area. Sysop Flags ................. Flags needed to be allowed EVERYTHING in this message area. Origin Line ................. Only for Echomail: if you do not specify this, the default origin line will be used (refer to F1 - Site Options) Use AKA ..................... The network address for this area (for Echomail & Netmail only). Reply Area .................. The area where replies to messages in this area should be posted. Useful for allowing users to reply to "To-All" messages. Set this to "0" (zero) if you want replies to go to this area. Sysop ....................... The user name for an "Area Sysop". A user with this name will have full Sysop access to this message area. When users write messages to "Sysop" in this area, the messages will be sent to the user name specified here. - 33 - Kill after <xx> days ........ When running the PBUtil message- packer with the -D parameter, all messages that have been in the messagebase for <xx> days will be deleted. Kill rcvd after <xx> days ... When running the PBUtil message- packer with the -D parameter, all messages that have been received for xx days will be deleted. Max # messages .............. The maximum number of messages allowed in this area. When this number is exceeded, PBUTIL MP -D (message pack & delete) will delete the oldest messages from the messagebase. ┌──────────────────────────────────────────────────────────────────┐ │ File areas - (F4) │ └──────────────────────────────────────────────────────────────────┘ File areas are used to categorize downloadable files. You can even prevent groups of users to access certain file areas. A file area has the following fields: Area Name ................... Name of this file area. Displayed to users on the BBS. Listing File ................ Full path & filename of the file in which the downloadable files are described. Refer to Menu Function 31, in the chapter on Menus. Sample: C:\PB\DLOAD\FILES.BBS) - 34 - File Location ............... Directory where the files for this area are located. It is also possible to specify multiple directories per file area. To do this, enter the first file directory here, then create a file in the ProBoard system directory (usually C:\PB) called FA_<area>.CTL. Place each additional file directory (one directory per line) in this file to tell ProBoard where to find the additional directories for this file area. Example: for file area #10 (Games), which has a total of 4 directories, place the first directory in the "File Location" slot in PROCFG, then create a file called FA_10.CTL. In this file, place the additional directories one per line like this: D:\DLOAD\GAMES2 D:\DLOAD\GAMES3 D:\DLOAD\GAMES4 Use an ascii editor like QEDIT to create this file. Access Flags ................ Flags needed to download files in this area. Access Level ................ Level needed to download files in this area. CD-ROM Option ............... Setting this option to 'Yes' makes the file listings look somewhat different. Refer to Menu Function 31, "List Files". In TOPFILES.................. Determines whether or not this file area is included when TOPFILES.A?? is created. Refer to PBUTIL FC for more information. Free Area ................... Specifies whether or not ALL files in this file area are FREE files. If this is set to 'Yes', any files a user downloads from this area will not be deducted from their download limits. - 35 - Max. files................... Maximum number of files that can be downloaded from this area per user per day (0 means unlimited). Max. Kb...................... Maximum number of Kbytes that can be downloaded from this area per user per day (0 means unlimited). ┌──────────────────────────────────────────────────────────────────┐ │ Time/Download Limits - (F5) │ └──────────────────────────────────────────────────────────────────┘ In ProBoard you can grant different groups of users different rights concerning download-limits and maximum online time per day. Additionally, you can limit downloading in a very powerful and flexible way. Editing user levels is done in by pressing <Ins>,<Del>, and <Enter>. These are the fields to be specified for each level: Security Level .............. The userlevel you are editing. Time Per Day ................ Time a user with this level can spend on your system each day. Kb Download Per Day ......... Daily download-limit associated with this user level (in Kbytes/day). Download Delay .............. Time to be spent per session before a download can be made (great to calm down excessive downloaders). Usergroup ID ................ String of max. 5 characters that identifies this level, eg. NEW, REG, VIP. This is optional. These ID's will be shown when the userlist is displayed (Refer to Menu Function 13). Free Download ............... The amount that can be downloaded by users with this level, without having to upload or write messages. - 36 - Upload Needed ............... The percentage of total downloads the user has to upload. Eg. if the upload factor is 15%, and a user has downloaded 1000Kb, he will have to upload 150Kb. Setting this to 0 allows the users to download as much as they want, until the download limit (see below) is reached. Of course, it is impossible to download more than the daily maximum each day. Free Download/Msg ........... The amount of Kilobytes that can be downloaded free for each message written. This rewards busy message- writers by increasing their download- limit. The amount of kilobytes is added to the free download number (see above) Maximum Download ............ When this limit is set to a positive non-zero value, and a user reaches this limit, his/her level will be changed to the "Fall To" level. Fall To Level ............... Security Level user should be assigned when their "Maximum Download" (above) is reached. ┌──────────────────────────────────────────────────────────────────┐ │ User Editor (F6) │ └──────────────────────────────────────────────────────────────────┘ Working with the user editor is easy. You can use the user editor to search for, look at, and change a user's data. You can edit users with the PROCFG utility. The editor activated by Alt-E in ProBoard is identical to the one in PROCFG. You can use the following keys in the user editor: <PgUp> Go to the previous user-record. <PgDn> Go to the next user-record. <Ctrl-PgUp> Go to the first user-record. <Ctrl-PgDn> Go to the last user-record. - 37 - <Alt-S> Search for a user-record. You may specify whole or part of a user's name. <Alt-N> Search for the next user-record complying to the name specified with <Alt-S>. <Alt-D> Toggle the 'deleted' flag of the current user. <Alt-A> Add a new user <F10> Opens a secondary window containing additional information about the current user. Once this window is displayed, you may display/edit the following items. - Times Called. - Total Number of Downloads. - Total KB of Downloads. - Total Number of Uploads. - Total KB of Uploads. - Number of Messages User has posted. - Total Time user has spent online to date. - Total KB downloaded today. When you have found the user-record you were looking for, move between the fields by using the arrow keys. To edit a field, just move the selector to that field and begin editing straight away (Insert is ALWAYS on). A user-record has the following fields: User Name ............ User's name. Password ............. User's password. City ................. City the user lives in. Country .............. Country (or state) the user lives in. Voice Phone # ........ User's voice phone number (not restricted to a certain layout). Europeans hate the restrictions in other BBS packages :-( Data/Fax Phone # ..... User's data or fax number (if any). Level ................ User's level (ranging from 0 to 64000). A 0 means that the user has NO access to the BBS. - 38 - Flags ................ User's flags. Edit them by pressing <Enter>, and then pressing any character ranging from A - Z and 1 - 6 to toggle that flag. Loglevel ............. The way in which the user will be logged in the logfile (more about this later). Alias ................ Each user can have a unique 'alias' (nickname). In selected message areas, the user can use this alias to write messages or (if enabled) can login using this alias. Netmail credit ....... Number of credits the user has left to write Netmail messages. Screen Length ........ number of screen lines for this user. Expiration Date ...... When this date is specified (non-zero), the user's security level will drop to the level specified in the Expiration Level field (below). Expiration level ..... The new security level assigned to a user when the expiration date (if other than 0) is reached. Comment .............. This field allows you to enter comments about this particular user. Birth Date ........... The date of birth of this user. First Call ........... The date of the user's first call to the system. Hidden ............... If enabled, ProBoard will hide this users activity from the Last Callers list (Function 51), Show Users Online (Function 50), and from the display of the User List (Function 13). Deleted .............. If a user is set to deleted, his record will be removed from USERS.BBS upon the next user pack. ANSI ................. Should ANSI codes be sent to the user? AVATAR ............... Should AVATAR codes be sent to the user? - 39 - More Prompt .......... Pause after each screen? Clear Screen ......... Send screen clearing codes to the user? Stacking ............. Use command-stacking/hot keys (toggle). No-IBM ............... Determines whether all the IBM-specific characters should be filtered out and converted to standard ASCII. Full Screen Editor ... Use the fullscreen message editor or the internal line editor? NoKill ............... The user's record CAN NEVER be removed from the userfile. Ignore Download ...... Does the user have UNLIMITED download access? Attention ............ ProBoard will beep or play a song when this user tries to log in. In Tops .............. If enabled, this user will be shown in 'tops' lists (Menu Function 48) ┌──────────────────────────────────────────────────────────────────┐ │ Menu Editor (F7) │ └──────────────────────────────────────────────────────────────────┘ Creating Menus for ProBoard is extremely easy using the built-in Menu Editor. Basically, each line of your menus that your users will see contains the following attributes. Text Line ................... Text line to be displayed to the user. HotKey ...................... The key the user is to press to activate this menu option. Function .................... Function to be executed. Data ........................ Data associated with this menu item. Level ....................... Security level users needs to access this menu item. Flags ....................... The flags that the user needs in their user record to access this menu item. - 40 - Color ....................... Color of this menu item. When you select the 'Menu Editor' option in PROCFG's main menu, a new window will be opened containing the menus already available. In this window, you can use the following keys: - Up/Down Scroll up/down. - Enter Select a menu. - Ins Add a menu. When you have selected a menu, a list of all the menu items will be displayed. To add a menu item, just move past the last item and press <Enter>. To insert an item, press <Ins>, to remove one, press <Del>. To edit a menu item, move the selector to that item and press <Enter>. You can change the menu prompt and highlight colors by pressing <Alt-P>. If you want to see how a menu will look like, press <Alt-S>. You can also copy and paste menu items. To copy an item, move to the item you want to copy, and press <Alt-C>. To insert the copied item somewhere else, move to the place where you want the menu item, and press <Ctrl-P>. You can even copy and paste items across different menus. ┌──────────────────────────────────────────────────────────────────┐ │ Matrix Addresses (F8) │ └──────────────────────────────────────────────────────────────────┘ This is where you enter your net address. If you have more than one net address, enter them here also. ┌──────────────────────────────────────────────────────────────────┐ │ Modem Parameters - (F9) │ └──────────────────────────────────────────────────────────────────┘ You don't have to change these parameters when using ProBoard with a mailer. Should ProBoard, however, need to answer the phone, you may want to take a look at (and change) these parameters. - 41 - You can insert special codes in the modem command strings: ^ Set DTR high. ` or v Set DTR low. | Sends a <CR> to the modem. $ Sends a break to the modem. ~ Pauses for 1/2 second. Max. Baud Rate .............. Maximum baud rate your modem can handle. Com-port .................... Number of the com-port the modem is connected to (1-8). Blanktime (s) ............... Time after which the (YOUR) screen goes blank, to prevent burn-in. Modem Delay ................. Number of 1/10 seconds to pause between each character that is sent to the modem (some modems can't handle FAST input). Init String ................. String to be sent to the modem to initialize it and to have the modem ready to answer the phone. You can use text macros in this string. This can be useful for specifying a different init string for each node. Init Response ............... String returned by the modem if the initialization was successful. Busy String ................. String to be sent to the modem when the BBS is off-line (because Sysop pressed <Esc> or is logging in locally). Manual Answer ............... If enabled, ProBoard will answer the phone manually by sending the answer string when the ring string is received. Do NOT set your modem in auto-answer mode when using this option. RING String ................. The string the modem sends to ProBoard when a call is coming in. Usually, this is set to "RING". - 42 - Answer String ............... The command ProBoard sends to the modem to answer the phone. Usually, this is set to "ATA". XXX Bps Call ................ String returned by the modem upon an XXX bps call. This is a 'partial' string. So if the modem sends 'CONNECT 2400/ARQ', the string 'CONNECT 2400' will match. A '|' can be used to specify a CR. It HAS to be used for the 300 bps connect string, because "CONNECT" without a '|' would match "CONNECT 2400" or "CONNECT 9600". So the correct string is: "CONNECT|". LOCKING BAUD RATES ────────────────── Note: If you use an error-correcting modem (MNP/V42), you have to lock your serial port speed. A "locked" baud rate refers to the tranfer rate between the computer and modem. When locked, the baud rate will remain constant regardless of what the application program, such as ProBoard, requests the baud rate to be. The modem MUST support a constant computer to modem speed, otherwise any baud rate change requested by an application will be ignored, resulting in an incorrect setting between your system and your users. The result will be garbled input and output. Most high speed modems do support a fixed baud rate, and by locking the baud rate you will obtain higher throughput. A fossil program like X00 or BNU will handle this for you and is HIGHLY RECOMMENDED (see the respective fossil doc file for command syntax). Note: Experience shows that a faster locking baud rate than actual phone line baud rate will yield the best results. Examples: X00 B,0,9600 BNU /L0=9600 See your FOSSIL documentation for details. If possible, install your fossil for "quiet" or "no commercial" mode so the screen display from the fossil does not bleed onto the ProBoard main screen (stand-alone systems with no mailers in particular). - 43 - ┌──────────────────────────────────────────────────────────────────┐ │ Events - (Shift-F1) │ └──────────────────────────────────────────────────────────────────┘ It is possible to instruct ProBoard to perform some action at a set time and day (an "Event"). This action can be: exiting with a specific errorlevel (for a batch file) or executing a DOS command. This is useful for example, to pack the user file, or to pack the message base at a specified time each day. You can define up to 30 events. An event is described by the following fields: Enabled...................... If this is set to 'No', the event will be ignored. Active Days.................. Determines on what days of the week this event will run. To edit this field, press <Enter> and toggle the 'Yes/No' fields displayed next to each day. Event Time................... The time at which the event has to run on the selected days (in 24h format). Duration..................... How long this event has to stay active. During the event, no users are allowed to log in on ANY node. Event type................... 'Command' : A DOS-command will be executed when the event is activated. You can use any of the shell options from menu type 7. Remember to use the *Z option to run a batch file. 'Errlevel': When the event is activated, ProBoard will exit with an errorlevel, specified in the next field. Errorlevel................... The errorlevel to use for this event if the event type is set to 'Errorlevel'. - 44 - DOS-command.................. The DOS-command to execute for this event if the event type is set to 'Command'. Node number.................. An event will run on ONE node. You can specify the node here. When using a frontend-mailer, you only have to specify the time, days and duration, because the events have to be executed by the mailer. ┌──────────────────────────────────────────────────────────────────┐ │ Personal Files - (Shift-F2) │ └──────────────────────────────────────────────────────────────────┘ ProBoard allows you and other users to send "Personal Files" to each other on the BBS. ProBoard keeps track of each uploaded file. You add/edit/delete them with this option in ProCFG. In the list of files, a [+] means that the file physically exists in the private upload directory (the path you set in your configuration). To edit an entry, press <Enter>, to Delete an entry, press <Del>, and to add an entry, press <Ins>. Filename..................... Name of the uploaded file. From User.................... Who uploaded this file? To user...................... The destination user of this file. Date......................... The date on which this file was uploaded. It is possible to add files to this list. This way you can send a file to a specific user. Deleting files is possible too. If the file specified in the entry to be deleted physically exists, you will be asked if you want to delete the file on disk. For more information on how to implement this option on your BBS, refer to Menu Function(s) 22, 33, 32 explained in detail in the section on menus. - 45 - ┌───────────────────────────────────────────────────────────────────┐ │ Edit Statistics (Shift-F3) │ └───────────────────────────────────────────────────────────────────┘ Hourly Statistics ............ Pressing <ENTER> will display a window with the hours that are displayed on your system usage graph. You can edit them so your hourly graph looks different. Weekly Statistics ............ Pressing <ENTER> will display a window with the weekly information that is displayed on your system usage graph. You can edit this info so your weekly graph looks different. - 46 - ╒═══════════════════════════════════════════════════════════════════╕ │ ░░░░░░ SECURITY ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘═══════════════════════════════════════════════════════════════════╛ ┌──────────────────────────────────────────────────────────────────┐ │ Levels & Flags │ └──────────────────────────────────────────────────────────────────┘ All security procedures toward a user are being done through the user's LEVEL and FLAGS. ProBoard can have levels ranging from 0 to 64000, and provides 32 flags (A-Z, and 1-6) that can be ON or OFF. If a menu needs a certain level and flags, then only the users with a level equal to or higher than that level and with all the needed flags will be able to SEE and CHOOSE this menu option. It will remain invisible to all the other users. An example will be given in the next chapter. ┌──────────────────────────────────────────────────────────────────┐ │ Trashcan │ └──────────────────────────────────────────────────────────────────┘ It is possible to specify names that cannot be used to log on to your system. Often used fake names are: "Sysop", "BBS", etc... You can specify these names in a textfile called TRASHCAN.CTL. Each line in this file specifies an unwanted or illegal name. An example file is included. - 47 - ┌──────────────────────────────────────────────────────────────────┐ │░░░░░░ MENUS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────┘ This is the most important part of a BBS, and therefore of ProBoard. Menus are the direct interface between a user and your BBS. They are used to execute all the BBS functions, and they can have their own submenus. They take care of security, by disabling or hiding certain functions from certain users or groups of users. ProBoard can make your BBS have a very personal look, as the menus can be built/displayed in a VERY flexible way. ┌──────────────────────────────────────────────────────────────────┐ │ Setting Up Menus │ └──────────────────────────────────────────────────────────────────┘ A menu is basically line-oriented. Every line is linked to a function to be executed and to a textline to be shown to the user. Every line/function has its own level and flags, to make sure that not all of the menu items are available to every user. A menu line has the following fields: Textline..................... Textline to be displayed to the user. Hotkey....................... Key to be pressed by the user to activate this menu item. Function..................... Function to be executed. Data......................... Data associated with this menu item. Level........................ Level needed to access this menu item. Flags........................ Flags needed to access this menu item. Color........................ Color of the menu line. - 48 - ┌──────────────────────────────────────────────────────────────────┐ │ Menu Security │ └──────────────────────────────────────────────────────────────────┘ To clarify menu security, here's a simple example: Suppose we have 4 users with the following levels and flags: ┌──────────────────────┬───────┬─────────┐ │ Name │ Level │ Flags │ │----------------------│-------│---------│ │ Pete │ 10 │ Z │ │ Jerry │ 100 │ P │ │ Al │ 100 │ R │ │ Charlie │ 200 │ P & R │ └──────────────────────┴───────┴─────────┘ Let's define a menu with textlines only: ┌───────────────────────┬───────┬────────┐ │ Text │ Level │ Flags │ │-----------------------│-------│--------│ │ Good morning; │ 10 │ │ │ ,; │ 50 │ │ │ Jerry │ 100 │ P │ │ and; │ 150 │ │ │ Al; │ 100 │ R │ │ send their best wishes│ 200 │ P & R │ │ . │ 300 │ │ │ :-) │ 10 │ X │ └───────────────────────┴───────┴────────┘ This would give the following result when the menu is displayed: ┌─────────────────┬─────────────────────────────────┐ │ Pete │ Good morning │ ╞═════════════════╪═════════════════════════════════╡ │ Jerry │ Good morning,Jerry │ ╞═════════════════╪═════════════════════════════════╡ │ Al │ Good morning,Al │ ╞═════════════════╪═════════════════════════════════╡ │ Charlie │ Good morning, Jerry │ │ │ and Al send their best wishes │ └─────────────────┴─────────────────────────────────┘ The last 2 lines of the menu will NEVER be displayed, because none of the 4 users have the required level AND flags. - 49 - ┌──────────────────────────────────────────────────────────────────┐ │ Creating Menus │ └──────────────────────────────────────────────────────────────────┘ Your BBS's main menu MUST! be stored in a file called TOP.MNU. All the other menus can have any file name you want to give them. When you select the 'Menu Editor' option in PROCFG's main menu, a new window will be opened containing the menus already available (if any). In this window, you can use the following keys: - Up/Down Scroll up/down. - Enter Select a menu. - Ins Add a menu. When you have selected a menu, a list of all the menu items will be displayed. To add a menu item, just move past the last item and press <Enter>. To insert an item, press <Ins>, to remove one, press <Del>. To edit a menu item, move the selector to that item and press <Enter>. You can change the menu prompt and highlight colors by pressing <Alt-P>. If you want to see how a menu will look, press <Alt-S>. You can also copy and paste menu items. To copy an item, move to the item you want to copy, and press <Alt-C>. To insert the copied item somewhere else, move to the place where you want the menu item, and press <Ctrl-P>. You can even copy and paste items across different menus. A menu item has the following fields: Textline..................... This is the string to be displayed. Leaving this field blank causes a blank line to be displayed to the user. A CR/LF will be sent after the menu line. To avoid this, just enter a ';' as the last character. This will cause the next textline of the menu to be appended to this one. - 50 - Special textline characters: ^ : Switches between normal and highlighted color. ~ : Replaced by the number of minutes the user has left in this session. ` : Replaced by the name of the current message area (more about this later). @ : Replaced by the name of the current file area (more about this later). This textline can also contain text macros like @<NAME>@ or @<NODE>@. More about this in the "Text macros" section. You are not limited to two colors in menu lines. You can use the codes \1 to \7 to change colors, or \0 to return to the original color. Hotkey....................... Most of the menu functions must be chosen by the user, so ProBoard must react to certain key-presses from the user. Receiving the hotkey for a certain menu item will cause ProBoard to execute the function associated with this item. The hotkey can be any ASCII character or digit,but one character has a special meaning to ProBoard: <Ctrl-A> will make this function AUTOEXEC, which means that this function will be executed as soon as this menu item is displayed (without really selecting this option). Function..................... The function associated with this menu item. Pressing the <Enter> key will cause a complete list of all the menu functions to be displayed in a separate window. - 51 - Data......................... This field is optional with some of the functions. Basically, in this field you enter the parameters of a menu function. Eg. function 40 (Display ASC/ANS file) needs a file- name as data (parameter). Function 1 (Goto menu) needs the name of the menu to be jumped to. Text macros can be inserted (see "Text macros" section). Level........................ Level needed to access this menu item. Flags........................ Flags needed to access this menu item. Color........................ Color for the menu's textline to be displayed in. ┌──────────────────────────────────────────────────────────────────┐ │ Hints │ └──────────────────────────────────────────────────────────────────┘ You can create a menu by using textlines, but you can also create menus that display a file to the user, in which all the options are shown. This technique works as follows: The first item in the menu should have ';' as textline and <Ctrl-A> (autoexec) as hotkey. The function to be executed should be function 40 (Display file with hotkeys). When the user accesses this menu, the specified file will immediately be sent. Setting all the remaining textlines of the menu to ';' will cause NOTHING BUT this file to be displayed. Combined with the use of text macros, this allows you to show different looking menus for each node you are running. For example, if you use function 40, and enter "MAIN@<NODE>@" in the data field, node 1 will see file MAIN1 , node 2 will see MAIN2, etc... This feature could be used to create a completely different set of menus for each node on your board! If you need more information about all the possiblities, take a look at the example menus. - 52 - ┌──────────────────────────────────────────────────────────────────┐ │ Menu Function Summary │ └──────────────────────────────────────────────────────────────────┘ The following is a summary list of the ProBoard Menu Functions. Each Menu Function is explained in detail in the following section titled "Menu Functions Overview". Function Action Performed Page ─────────── ────────────────────────────────────────── ──── Function 1 .... GOTO Menu ................................ 55 Function 2 .... GOSUB Menu ............................... 56 Function 3 .... GOTO Previous Menu ....................... 58 Function 4 .... GOTO Menu and Clear Menu Stack ........... 58 Function 5 .... Show ANS/ASC File......................... 59 Function 6 .... Change State/Country...................... 59 Function 7 .... Shell .................................... 59 Function 8 .... Show Version Information ................. 62 Function 9 .... Log Off .................................. 62 Function 10 ... Show System Useage Per Hour (Graph) ...... 62 Function 11 ... Chat Request ............................. 63 Function 12 ... Execute Questionaire Script .............. 63 Function 13 ... Display User List ........................ 67 Function 14 ... Display Time Info ........................ 67 Function 15 ... Show A?? File and Wait ................... 67 Function 16 ... Change City .............................. 67 Function 17 ... Change Password .......................... 68 Function 18 ... Change Screen Length ..................... 68 Function 19 ... Toggle Screen Clearing Codes ............. 68 Function 20 ... Toggle More Prompt ....................... 69 Function 21 ... Toggle ANSI Codes ........................ 70 Function 22 ... Check for Personal Mail / Files .......... 70 Function 23 ... Read Messages ............................ 71 Function 24 ... Scan Messages ............................ 72 Function 25 ... Quick Scan Messages ...................... 72 Function 26 ... Show System Usage by Day (Graph) ......... 73 Function 27 ... Write a Message .......................... 73 Function 28 ... Combined Boards Select ................... 74 Function 29 ... Display System Useage Per Week (Graph).... 74 Function 30 ... Show Directory ........................... 74 Function 31 ... List Files ............................... 75 Function 32 ... Download a File .......................... 77 Function 33 ... Upload a File ............................ 78 Function 34 ... View an Archive .......................... 78 Function 35 ... File Search by Keyword ................... 79 - 53 - Function Action Performed Page ─────────── ────────────────────────────────────────── ──── Function 36 ... File Search by File Name ................. 78 Function 37 ... Show New Files ........................... 78 Function 38 ... View a File .............................. 80 Function 39 ... Display Named File ....................... 80 Function 40 ... Display A?? File with Menu HotKeys ....... 80 Function 41 ... Toggle the Full Screen Editor ............ 81 Function 42 ... Toggle Command Stacking/Hotkeys .......... 81 Function 43 ... Clear Marked Messages .................... 82 Function 44 ... Global Combined Boards Selection ......... 82 Function 45 ... Display Text File and Wait ............... 82 Function 46 ... Change User Level and/or Flags ........... 82 Function 47 ... Make a Log Entry ......................... 83 Function 48 ... Show Hit Parade .......................... 83 Function 49 ... Select Message Area ...................... 84 Function 50 ... Show Users Online ........................ 84 Function 51 ... List Last Callers ........................ 85 Function 52 ... Remote User Editor ....................... 85 Function 53 ... Multi-Line (Internode) Chat .............. 85 Function 54 ... Select File Area ......................... 86 Function 55 ... Show .GIF File Information ............... 86 Function 56 ... Toggle IBM Characters .................... 86 Function 57 ... Change Phone Number ...................... 86 Function 58 ... Change Data/Fax Phone Number ............. 87 Function 59 ... Change User Alias (Handle) ............... 87 Function 60 ... Run ProBoard SDK File .................... 87 Function 61 ... Bulletin Menu ............................ 88 Function 62 ... Toggle AVATAR/0 .......................... 88 Function 63 ... Toggle AVATAR/0+ ......................... 89 - 54 - ┌──────────────────────────────────────────────────────────────────┐ │ Menu Functions Overview │ └──────────────────────────────────────────────────────────────────┘ In this function overview, parameters between <> are REQUIRED, and parameters between [] are optional. For example: <blank> is a required parameter. [/M] is an option you might specify in addition. ┌──────────────────────────────────────────────────────────────────┐ │ Function 1: GOTO MENU │ └──────────────────────────────────────────────────────────────────┘ DATA: <menu name> [/M=<nr msgarea>] [/F=<nr filearea>] [/P=<pwd>] This function makes ProBoard jump to menu <menu name>. Option /M can be used to define one single menu for several message areas. You could jump to a 'general' message area menu and pass option /M=3, to make message area 3 active for the selected menu. Please refer to function 23 (Read messages) for more information about this option. Option /F works exactly the same, but applies to file areas. It is possible to protect a menu with a password by using the /P= option. For example: "SYSOP /P=Test" would protect menu "SYSOP" with the password "Test". The user will have to enter this password to be allowed to move to the menu. It is also possible to select the next available message or file areas with the use of the following parameters. /M=+ (set next accessible Message Area) /M=- (set previous accessible Message Area) /F=+ (set next available File Area) /F=- (set previous accessible File Area) Data examples: - 55 - MSG /M=5 ──────── This makes ProBoard GOTO the menu named "MSG" and sets the Message Area to Area #5. FILE /F=10 ────────── This makes ProBoard display the menu named "FILE" and sets the File Area to Area #10 MSG /M=+ ──────── This makes ProBoard display the menu named "MSG" and selects the next Message Area that is available to this caller. FILE /F=- ───────── This makes ProBoard display the menu named "FILE" and selects the previous File Area that is available to this caller. ┌──────────────────────────────────────────────────────────────────┐ │ Function 2: GOSUB MENU │ └──────────────────────────────────────────────────────────────────┘ DATA: <menu name> [/M=<nr msgarea>] [/F=<nr filearea>] [/P=pwd] - 56 - This function is largely the same as the Menu Function 1 (it even has the same parameters), but the menu this function is called from is pushed onto an internal stack. ProBoard will jump back to this menu when returning from menu <menu name> (by executing Menu Function 3). Data examples: (see Menu Function 1 for complete parameters) MSG /M=5 ──────── This makes ProBoard display the menu named "MSG" and sets the Message Area to Area #5. It also places the previous menu on a stack. The previous menu can be returned to by using Menu Function 3. FILE /F=10 ────────── This makes ProBoard display the menu named "FILE" and sets the File Area to Area #10. It also places the previous menu on a stack. The previous menu can be returned to by using Menu Function 3. MSG /M=+ ──────── This makes ProBoard display the menu named "MSG" and selects the next Message Area that is available to this caller. It also places the previous menu on a stack. The previous menu can be returned to by using Menu Function 3. FILE /F=- ───────── This makes ProBoard display the menu named "FILE" and selects the previous File Area that is available to this caller. It also places the previous menu on a stack. The previous menu can be returned to by using Menu Function 3. - 57 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 3: GOTO PREVIOUS MENU │ └──────────────────────────────────────────────────────────────────┘ DATA: - This function makes ProBoard go back to the previous menu if you used Menu Function 2. ┌──────────────────────────────────────────────────────────────────┐ │ Function 4: GOTO MENU & CLEAR STACK │ └──────────────────────────────────────────────────────────────────┘ DATA: <menu name> [/M=<nr msgarea>] [/F=<nr filearea>] [/P=pwd] This function performs the same tasks as Menu Function 1, but will clear the existing menu stack, thus preventing the user from returning to the previous menu. Data examples: (see Menu Function 1 for complete parameters) MSG /M=5 ──────── This makes ProBoard display the menu named "MSG" and sets the Message Area to Area #5. The menu stack will be cleared preventing return to any previous menus already on the stack. FILE /F=10 ────────── This makes ProBoard display the menu named "FILE" and sets the File Area to Area #10. The menu stack will be cleared preventing return to any previous menus already on the stack. MSG /M=+ ──────── This makes ProBoard display the menu named "MSG" and selects the next Message Area that is available to this caller. The menu stack will be cleared preventing return to any previous menus already on the stack. FILE /F=- ───────── This makes ProBoard display the menu named "FILE" and selects the previous File Area that is available to this caller. The stack will be cleared preventing return to any previous menus already on the stack. - 58 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 5: SHOW ANS/ASC FILE │ └──────────────────────────────────────────────────────────────────┘ DATA: <filename> This function displays a file to the user with the extension .ANS or .ASC, depending on the user's ANSI-setting. The file must be stored in ProBoard's textfiles directory; <filename> should NOT contain an extension (max. eight characters). If ProBoard doesn't find the .ANS file, it will look for the .ASC file. ┌──────────────────────────────────────────────────────────────────┐ │ Function 6: CHANGE COUNTRY │ └──────────────────────────────────────────────────────────────────┘ DATA: - Allows the user to change the country in his user-record. ┌──────────────────────────────────────────────────────────────────┐ │ Function 7: SHELL │ └──────────────────────────────────────────────────────────────────┘ DATA: <command line> With this function, you can instruct ProBoard to execute an external program. This program has to do its own serial I/O, so ordinary programs will only work if run locally. Parameter <command line> needs full path and filename (.COM or .EXE extension included), and may contain some special codes. These codes will (at run-time) be replaced by a value or a string. Special codes: ** Replaced by an asterisk ('*') *# Replaced by the node number. *\ Sends the message "Sysop is shelling..." to the user before the shell is executed, and the message "Sysop has returned..." afterwards. - 59 - *! Freezes ProBoard's system timer when shelling. *= Do not call any fossil functions when shelling. Great for use in INIT.PEX files. *A Writes a user's handle (alias) to DORINFOx.DEF instead of his/her real name. *B Current baud rate. *C Replaced by the full name & path of the command interpreter. It is the contents of the environment variable "COMSPEC". This usually is C:\COMMAND.COM. *D Writes a DOOR.SYS file to the current directory before shelling. *E Writes EXITINFO.BBS to the current directory before shelling and reads it back afterwards. *F User's first name. *G Indicates whether user has ANSI (1) or ASCII (0) set. *H Tells ProBoard not to disable the fossil driver when shelling. *I Maximum user-inactivity (seconds). *L User's last name. *M ProBoard's start-up directory (including trailing '\') *N Shell will NOT be logged in PROBOARD.LOG. *O (not zero!) is replaced by the path of the current file area. *P Com-port used by ProBoard (1-8). *Q Don't let user know that ProBoard is shelling (!). *R User's record number in USERS.BBS. *S ProBoard's system directory (incl. trailing '\') *T Time left for the user today (minutes). *V Disables adding 2 to the graphics capability line in DORINFOx.DEF when the user has AVATAR enabled. - 60 - *W Runs the shell in a window , so the status on the last line will not be cleared. This option only works with programs that send their output to the standard output device (no direct screen writes). *X ALWAYS SWAP to disk/EMS, even if swapping is enabled in ProCFG. *Y DO NOT SWAP to disk/EMS. *Z Execute the command as if you typed it from the command line. The main use for this option is to execute DOS batch files. It is exactly the same as entering "*C /C <command>". It can also be useful to execute programs that are located in your path, without having to specify the exact directory name. *_ (asterisk underscore) Tells ProBoard not to write underscores instead of spaces when writing a user's last name in DORINFOx.DEF. For example, users name is Harvey Van Hooten. Without this parameter, users name will be written to DORINFOx.DEF as follows: HARVEY VAN_HOOTEN By using the *_ (asterisk underscore) the users name will be written to DORINFOx.DEF as follows: HARVEY VAN HOOTEN (with no underscore in last name) *0 (zero) ProBoard will write a DORINFO1.DEF instead of a DORINFO<node>.DEF - great for running doors which require a DORINFO1.DEF file on a multi node ProBoard system. *1 Installs a timer-function when shelling, which continuously redisplays the user's status line on the first screenline. This can be used with ALL programs. (Works great most full-screen protocols!) *2 Same as *1, but uses the bottom screenline (try this with QuickEd!) Suppose ProBoard is in directory D:\PB. Data example: *Q*STEST.EXE *B ProBoard will execute D:\PB\TEST.EXE 2400 and the user won't see this happening. - 61 - To execute a batch file, you have to use the following syntax: "*Z<filename>.BAT <parameters>". This is expanded to: "*C /C <filename>.BAT <parameters>". When shelling, ProBoard writes a standard DORINFOx.DEF file, where x stands for the node-number. An RA-compatible EXITINFO.BBS file and a DOORWAY-compatible DOOR.SYS can also be created by specifying the *E and/or *D options. All these files are created in the directory where ProBoard is started from. ┌──────────────────────────────────────────────────────────────────┐ │ Function 8: SHOW VERSION INFORMATION │ └──────────────────────────────────────────────────────────────────┘ DATA: - This function shows information about ProBoard's version number. If you have a registered copy of ProBoard, the Sysop's name and BBS-name will be shown. With this function, you can show off to your users that you're a nice Sysop: one that registered! ┌──────────────────────────────────────────────────────────────────┐ │ Function 9: LOGOFF │ └──────────────────────────────────────────────────────────────────┘ DATA: - Shows the file GOODBYE.ANS/ASC and hangs up the phone. ┌──────────────────────────────────────────────────────────────────┐ │ Function 10: SHOW SYSTEM USAGE PER HOUR (GRAPH) │ └──────────────────────────────────────────────────────────────────┘ DATA: - Shows a bar graph of the average system usage per hour. From the day you install ProBoard, it will keep track of a usage rate per hour and per day. If you want to change the usage values, just edit the values using ProCFG. - 62 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 11: CHAT REQUEST │ └──────────────────────────────────────────────────────────────────┘ DATA: - This function allows the user to make a request to chat with the Sysop. The user will be prompted for a reason why he wants to chat. The minimal length of this reason must be 5 characters. If the Sysop does not answer, the status line will start flashing, indicating that the users wants to chat. You can view the reason for the chat by pressing <F8>. You can define your own page-tune by creating a RemoteAccess- compatible description file. The format of this file is described in the reference section. ┌──────────────────────────────────────────────────────────────────┐ │ Function 12: EXECUTE QUESTIONNAIRE SCRIPT │ └──────────────────────────────────────────────────────────────────┘ DATA: <scriptname> This function executes a questionnaire. A questionnaire is a common ASCII-file containing several commands to be executed by ProBoard. A questionnaire scriptfile has an extension .Q-A, and the user's answers will be stored in a file with the same filename, but with extension .ASW. Starting from version 1.15, you can write very powerful questionnaires by using the ProBoard SDK. You can use the following commands in a scriptfile: ASK <length> <number of variable> eg: Ask 10 1 Asks the user something. The user has <length> characters to answer, and the answer will be stored in the variable <number of variable>. The maximum number of variables in ProBoard is 20. - 63 - CHANGECOLOR <color> eg: ChangeColor 3 Changes the color in which the following text will be displayed. The number <color> is the ANSI color code, which means that this function works only for users who use ANSI. CLEARSCREEN Well, what do you think? DISPLAY "<string>" eg: Display "Hi there!" Displays a string <string>. The string must be contained in double quotes; a '|' in a string will be replaced by CR/LF (new line). IF <number of variable> = "<string>" eg. If 1 = "Y" Directs the .Q-A file according to the user's answers. If the condition is met, all commands after the IF-statement will be executed, until an ENDIF is encountered. ENDIF Ends an IF-statement. eg: Display "Do you have a hard disk?" GetChoice YN 1 If 1 = "Y" Display "Storage space in Mb?" Ask 2 EndIf Display "..." GETCHOICE <options> <number of variable> eg: GetChoice YN 1 Forces the user to give a proper answer, chosen from <options>. - 64 - OUTPUTANSWER ["<description>"] <number of variable> eg: OutputAnswer "Name: " 1 Writes ["<description>"] and the value in <number of variable> to the .ASW-file. <description> is optional. POSTINFO Writes a header to the .ASW-file. The header contains some general information about the user ("Peter Piper answered on ..."). QUIT Ends execution of the questionnaire script. SETFLAG <flag> <ON/OFF> eg: SetFlag C ON Sets/clears user flag <flag>. For compatibility with RA, it is also possible to use the QuickBBS/RA flags (A1-D8) SETSECURITY <level> eg: SetSecurity 20 Changes the user's security level. CAPITALISE [On|Off] eg: Capitalise On Changes the way input from the user is displayed. When ON, all characters typed will be converted to uppercase. - 65 - DISPLAYFILE <filename> eg: DisplayFile TEST Displays <filename>.ANS/ASC. It is identical to menu function 5. EXEC <command> eg: Exec "*ZECHO TEST" Execute a shell. It is identical to function 7. Note that you MUST use quotes (") if the command contains any spaces. LISTANSWER <var-num> eg: ListAnswer 4 Displays variable <var-num>, with a CR/LF at the end. MENUCMND <num> [data] eg: MenuCmnd 11 "Yelling Sysop..." Execute any menu command. If the data field contains spaces, you MUST use quotes ("). WAITENTER eg: WaitEnter Waits for the <Enter> key. - 66 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 13: DISPLAY USERLIST │ └──────────────────────────────────────────────────────────────────┘ DATA: - Prompts the user for a name (or part of a name) and goes looking for it in the name fields of USERS.BBS. If the user doesn't specify a string (if he presses <Enter>), the entire userlist will be displayed. ProBoard uses a built-in "fuzzy search" algorithm, which will locate specific users even if you misspell their name. ┌──────────────────────────────────────────────────────────────────┐ │ Function 14: DISPLAY TIME INFO │ └──────────────────────────────────────────────────────────────────┘ DATA: - Displays information about the current time, time online, remaining time, etc. ┌──────────────────────────────────────────────────────────────────┐ │ Function 15: SHOW ANS/ASC FILE & WAIT │ └──────────────────────────────────────────────────────────────────┘ DATA: <filename> Displays an ANS/ASC-file (like function 5) and waits for the user to press <Enter>. ┌──────────────────────────────────────────────────────────────────┐ │ Function 16: CHANGE CITY │ └──────────────────────────────────────────────────────────────────┘ DATA: - Allows the user to change the city in his user-record. - 67 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 17: CHANGE PASSWORD │ └──────────────────────────────────────────────────────────────────┘ DATA: - Allows the user to change his password. ┌──────────────────────────────────────────────────────────────────┐ │ Function 18: CHANGE SCREENLENGTH │ └──────────────────────────────────────────────────────────────────┘ DATA: - Allows the user to change his screen's length (# lines). ┌──────────────────────────────────────────────────────────────────┐ │ Function 19: TOGGLE CLEARSCREEN CODES │ └──────────────────────────────────────────────────────────────────┘ DATA: <blank> or <parameter> Allows the user to decide whether he wants clearscreen-codes sent or not. In the data field, you can enter these parameters: Ask Will ask for new status On Toggles option on Off Toggles option off Toggle Toggles option (reverse of current condition) Save Save current status for this option Restore Restore status saved by "Save" /Q Quiet. Do not display "xxxx is now enabled/disabled" Example: "Ask /Q" This will ask the user if they want to enable or disable screen clearing and ProBoard will not display: "Screen Clearing is now enabled/disabled". "Toggle" parameter. - 68 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 20: TOGGLE MORE PROMPT │ └──────────────────────────────────────────────────────────────────┘ DATA: <blank> or <parameter> Allows the user to decide whether scrolling should pause when the screen is full. In the data field, you can enter these parameters: Ask Will ask for new status On Toggles option on Off Toggles option off Toggle Toggles option (reverse of current condition) Save Save current status for this option Restore Restore status saved by "Save" /Q Quiet. Do not display "xxxx is now enabled/disabled" Example: "Ask /Q" This will ask the user if they want to enable or disable the More? prompt, and ProBoard will not display: "Page Pausing is now enabled/disabled". "Toggle" parameter. - 69 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 21: TOGGLE ANSI CODES │ └──────────────────────────────────────────────────────────────────┘ DATA: <blank> or <parameter> Allows the user to choose ANSI graphics/colors or not. In the data field, you can enter these parameters: Ask Will ask for new status On Toggles option on Off Toggles option off Toggle Toggles option (reverse of current condition) Save Save current status for this option Restore Restore status saved by "Save" /Q Quiet. Do not display "xxxx is now enabled/disabled" Example: "Ask /Q" This will ask the user if they want to enable or disable ANSI, and ProBoard will not display: "ANSI codes enabled/disabled". "Toggle" parameter. ┌──────────────────────────────────────────────────────────────────┐ │ Function 22: CHECK FOR PERSONAL MAIL & FILES │ └──────────────────────────────────────────────────────────────────┘ DATA: <blank> or [/F] or [/M] or both. Searches all the message areas for messages addressed to the user that have not yet been received by him/her. If ProBoard finds an area with new mail, which the user does not have read access to, it will inform the user, and the Sysop. This function also checks for personal files addressed to him/her. Specifying the [/F] option will force ProBoard to check only for new personal files. Specifying the [/M] option will force ProBoard to check only for new personal mail. - 70 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 23: READ MESSAGES │ └──────────────────────────────────────────────────────────────────┘ DATA: <area> or <*> or <0> Allows the user to read a message. If <area> is specified (a number ranging from 1 to 200), then only messages from message area <area> can be read. If <*> is specified, only messages from the active area can be read (refer to the goto/gosub menu functions and to function 49). If <0> is specified, only messages from areas selected in the combined boards can be read. When reading messages in combined message areas, messages are read "per area", not in the order of the message number. The user has several options when reading messages: Forward : First to last. Reverse : Last to first. New : New messages not read by the user. Messages are read per area. If you have new messages in Area 1 and 5, ProBoard will first show all new messages in Area 1, then all new messages in Area 5. Selected : Messages selected by name or subject. Marked : Marked messages only. When a message is read, the user has the following options: Next : Next message. Previous : Previous Message Again : Show this message again. Stop : Stop reading messages. Mark : Mark this message for later use. Reply : Reply to this message. The entire message will be passed to the external fullscreen editor, thus making it possible to quote text from the original message in your reply. - 71 - Unread : Set this messages status to 'Not received'. Moves to the next message (if any). Delete : Delete this message from the message base. Forward : Copy the message and address it to somebody else. This will only work in a LOCAL message area. Move : Move this message to an other message area. Private : Toggles the private/public status of the message. Export : Export this message to any file. + / - : Show the next/previous message in the reply-chain. Original : Go back to the message where you first used +/- to follow replies. ┌──────────────────────────────────────────────────────────────────┐ │ Function 24: SCAN MESSAGES │ └──────────────────────────────────────────────────────────────────┘ DATA: <area> or <*> or <0> Gives an overview of the messages. Only the message-header will be displayed, and the user has the possibility to mark messages for later retrieval. The options follow the same rules as in function 23 (Read messages). ┌──────────────────────────────────────────────────────────────────┐ │ Function 25: QUICKSCAN MESSAGES │ └──────────────────────────────────────────────────────────────────┘ DATA: <area>/<*>/<0> Same as the previous function, but only an overview in short form is displayed. The user does not have the possibility to mark messages. The options follow the same rules as in function 23 (Read messages). - 72 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 26: USAGE GRAPH BY DAY (GRAPH) │ └──────────────────────────────────────────────────────────────────┘ DATA: - Displays a graph of your system's use for the last <xx> days. The parameter <xx> is determined by the setting in PROCFG, under Options (F1), System Options, # Usage Graph Days. ┌──────────────────────────────────────────────────────────────────┐ │ Function 27: WRITE A MESSAGE │ └──────────────────────────────────────────────────────────────────┘ DATA: <area> or <*> [/L] [/T="<name of addressee>"] Allows the user to write a message. The area <area> (a number ranging from 1 to 200) can be replaced by <*> (refer to function 23). Optional parameters: /L The user will be logged off after writing this message. /T The destination (the addressee's name) is automatically specified. It is not necessary to use quotes (") when the username does not contain spaces. eg: /T=Sysop Writes a message to the sysop. /T="Peter Piper" Writes a message to Peter Piper. ProBoard's new "fuzzy search" will assist users who enter another users name improperly when they are writing messages in local areas. ProBoard will search the user file, and give the user a choice of all users whose names are close to what they typed. Great for entering messages to users with uncommon names such as "Philippe Leybaert", etc. ;-) - 73 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 28: COMBINED BOARDS SELECT │ └──────────────────────────────────────────────────────────────────┘ DATA: <blank> or [/M] Allows the user to select multiple message areas when using the 'combined boards read/scan' function. This is useful when a user is not interested in certain message areas. Also allows users to select which areas ProBoard will check [/M] for new mail. This is very useful for visiting Sysops who don't want to be forced to read echomail they already received on their own system. ┌──────────────────────────────────────────────────────────────────┐ │ Function 29: SYSTEM USAGE PER WEEK (GRAPH) │ └──────────────────────────────────────────────────────────────────┘ DATA: - Displays a graph of the system-usage in percent for the last 24 weeks. ┌──────────────────────────────────────────────────────────────────┐ │ Function 30: SHOW DIRECTORY │ └──────────────────────────────────────────────────────────────────┘ DATA: [directoryname] Shows a list of all the files stored in the specified directory. If no directory is given, the user will be prompted for one. - 74 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 31: LIST FILES │ └──────────────────────────────────────────────────────────────────┘ DATA: <area> or <X> Lists the files in the specified file area. If <X> was specified, the files in the active file area will be shown. The list of these files must be stored in a textfile created by the Sysop (refer to file area configuration). This textfile should contain the names and descriptions of the files. The description can be of any form you like. A line in the textfile should look like this: a) <filename> <blanks> <description> Filename + date + size + description will be displayed in the appropriate colors. b) <+> <description> The <+> will cause the description to be placed at the same horizontal cursor position and in the same color as the description from (a). This line will be displayed when searching for files. c) <!> <description> The description will be placed at the left of the screen, in the same color as the descriptions above. This line will be displayed when searching for files. d) <;> <description> Same as in (c), but the color is white. e) <description> Same as in (d), but this line will NOT be displayed when searching for files. - 75 - Example: ============================================================= PB_121.ARJ ProBoard version 1.21 +Best BBS program in the world !Original Belgian Product ;Flanders' Technology !!! ============================================================= This will be output as: ============================================================= [c2] PB_121.ARJ 18/12/90 268583 ProBoard version 1.21 [c1] Best BBS program in the world [c1] Original Belgian Product [c1] Flanders' Technology !!! [c2] ============================================================= [c2] [c1] stands for color 1, [c2] stands for color 2. If a file area is configured as being CD-ROM, the file listing should look slightly different. Option (a) will become: a) <filename><blanks><date><blanks><filesize><blanks><description> There is one more thing you can do to make your file listings more colorful (previously undocumented) : Inserting Ctrl-A to Ctrl-G characters in your file listing will change the color to: Ctrl-A Red Ctrl-B Green Ctrl-C Yellow Ctrl-D Magenta Ctrl-E Blue Ctrl-F Cyan Ctrl-G White - 76 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 32: DOWNLOAD A FILE │ └──────────────────────────────────────────────────────────────────┘ DATA: <area selection> or </A> or </F<filename>> or </P> Allows the user to download a file. The file areas a user can download from are defined by the area selection. This is a list of area-specifications, separated by blanks. Each specification has the form: [+]<area> <-><area> '+' stands for 'Include this area in the area-list', and is optional. '-' stands for 'Exclude this area from the area-list'. The parameter <area> should be one of the following: * All areas. C CD-ROM areas only. X Currently active area. <n> Area number <n>. <n1-n2> Areas <n1> to <n2>. Examples: * All areas * -C All non-CD-ROM areas. * -3-9 +5 Areas 1,2,5,10,11,... X +2 Active area + area 2. C -2 All CD-ROM areas, except area 2 Of course, a user must have the necessary download-rights in an area to be allowed to download files from it. You can also specify 3 other parameters: /A Allows the user to download ANY file accessible by DOS. When using this option, the full path and filename must be specified. This option is only intended for remote Sysops. - 77 - /F<filename> The user will not be prompted for a file, but the file <filename> will immediately be sent to the user (useful for textfiles describing all the files on the BBS). Parameter <filename> should contain the full pathname (eg. /FC:\PB\PB.DOC). /P The user can only download personal files addressed to him. ┌──────────────────────────────────────────────────────────────────┐ │ Function 33: UPLOAD A FILE │ └──────────────────────────────────────────────────────────────────┘ DATA: [directory] or [/P] Allows the user to upload a file to the BBS. If [directory] is specified, the upload will be placed in that directory. If not, it will be placed in the default upload-directory specified in PROCFG. (unregistered versions will always use the default upload directory). Upon successful reception of the file, the user will be prompted for a description of that file. The description can be several lines. If it begins with a '/', this description will be written to the file FILES.PVT in the upload-directory, else it will be written to the file FILES.BBS. If the data field contains "/P", the user can upload a personal file to another user. In this case the upload will be placed in the private upload directory (specified in ProCFG). ┌──────────────────────────────────────────────────────────────────┐ │ Function 34: VIEW ARCHIVE │ └──────────────────────────────────────────────────────────────────┘ DATA: <area selection> View the contents of a ZIP/LZH/ZOO/ARC/ARJ-file. The file specification input by the user will be looked for in the areas specified in <area selection>. Please refer to function 32 (Download) for more information. - 78 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 35: KEYWORD SEARCH │ └──────────────────────────────────────────────────────────────────┘ DATA: <area selection> Looks for a character string in the file descriptions. If the string is found, the related file and its description will be displayed. The character string will be looked for in the areas specified in <area selection>. Please refer to function 32 (Download) for more information. ┌──────────────────────────────────────────────────────────────────┐ │ Function 36: FILENAME SEARCH │ └──────────────────────────────────────────────────────────────────┘ DATA: <area selection> Looks for a filename in the file listings (wildcards allowed). The filename will be looked for in the areas specified in <area selection>. Refer to function 32 (Download) for more information. ┌──────────────────────────────────────────────────────────────────┐ │ Function 37: SHOW NEW FILES │ └──────────────────────────────────────────────────────────────────┘ DATA: <area selection> Shows a list of files more recent than a date specified by the user. If the user does not specify a date, then that date will be the last time this user logged in. The files will be looked for in the areas specified in <area selection>. Please refer to function 32 (Download) for more information. - 79 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 38: VIEW A FILE │ └──────────────────────────────────────────────────────────────────┘ DATA: <directory> This functions asks for a filename, and then looks for (and shows) the file stored in <directory>. ┌──────────────────────────────────────────────────────────────────┐ │ Function 39: DISPLAY NAMED FILE │ └──────────────────────────────────────────────────────────────────┘ DATA: <full filename> Displays a file to the user. The data field <full filename> must contain path, name and extension. ┌──────────────────────────────────────────────────────────────────┐ │ Function 40: DISPLAY ANS/ASC FILE WITH MENU HOTKEYS │ └──────────────────────────────────────────────────────────────────┘ DATA: <filename without extension> This function is the same as function 5, but can only be used in 'autoexec-menus', because it shows an ANS/ASC-file AND checks for menu hotkeys at the same time. Please refer to the section about menus for more information about the autoexec-concept. - 80 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 41: TOGGLE FULLSCREEN EDITOR │ └──────────────────────────────────────────────────────────────────┘ DATA: <blank> or <parameter> Lets the user decide whether they want to use ProBoard's line editor or the (external) fullscreen editor. In the data field, you can enter these parameters: Ask Will ask for new status On Toggles option on Off Toggles option off Toggle Toggles option (reverse of current condition) Save Save current status for this option Restore Restore status saved by "Save" /Q Quiet. Do not display "xxxx is now enabled/disabled" Example: "Ask /Q" This will ask the user if they want to enable or disable the full screen (external) editor, and ProBoard will not display: "Full Screen editor is now enabled/disabled". "Toggle" parameter. ┌──────────────────────────────────────────────────────────────────┐ │ Function 42: TOGGLE COMMAND STACKING │ └──────────────────────────────────────────────────────────────────┘ DATA: - Lets the user decide whether he will work with hotkeys or with combinations of hotkeys and command stacking (à la Opus). The command stack execution is initiated by pressing <Enter>. A ';' in the command stack will be replaced by <Enter>. Eg. M1WSysop;Subject;Y This would write a private message in message area 1 to the Sysop, with subject "Subject". - 81 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 43: CLEAR MARKED MESSAGES │ └──────────────────────────────────────────────────────────────────┘ DATA: - Clears all marked messages. ┌──────────────────────────────────────────────────────────────────┐ │ Function 44: GLOBAL COMBINED BOARDS SELECTION │ └──────────────────────────────────────────────────────────────────┘ DATA: - Allows the user to select or unselect all areas in his combined boards selection. ┌──────────────────────────────────────────────────────────────────┐ │ Function 45: DISPLAY TEXTFILE & WAIT │ └──────────────────────────────────────────────────────────────────┘ DATA: <full filename> Displays a textfile to the user, then waits for the user to press <Enter>. The filename requires full path, name and extension. ┌──────────────────────────────────────────────────────────────────┐ │ Function 46: CHANGE USER LEVEL AND/OR FLAGS │ └──────────────────────────────────────────────────────────────────┘ DATA: [level] [flag +/-] [flag +/-] ... Changes a user's level and/or flags. [level] can occur only once in the parameter array, flags can be toggled on/off by specifying the flag, followed by +/-. Data example: 10 A+ 3- This would set the user's level to 10, set flag A and clear flag 3. - 82 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 47: MAKE A LOG ENTRY │ └──────────────────────────────────────────────────────────────────┘ DATA: <log entry> Writes <log entry> to PROBOARD.LOG, thus allowing the Sysop to customize his log. ┌──────────────────────────────────────────────────────────────────┐ │ Function 48: SHOW HITPARADE │ └──────────────────────────────────────────────────────────────────┘ DATA: <Mn>/<Kn>/<Tn>/<Un>/<Fn>/<Cn>/<On> This functions returns an overview of the most active users in several fields. The 'n' with the parameters stands for the number of users to be displayed in the hitparade. (unregistered versions default to 5) M Best message-writers K Best downloaders (Kb) T Best downloaders (# downloads) U Best uploaders (Kb) F Best uploaders (# uploads) C Best callers (# times called) O Total time online Data example: U15 - 83 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 49: SELECT MESSAGE AREA │ └──────────────────────────────────────────────────────────────────┘ DATA: <area selection> Lets the user select a new message area. This function is to be used in cooperation with other message-related functions. Valid area selection parameters are: X Current Area E All Echo Areas N All NetMail Areas L All Local Areas * All Areas <n> Area #<n> <n1>-<n2> Areas #<n1> to #<n2> Examples: * -E All non-echomail areas 1-20 50-60 Areas 1..20 and 50..60 N 10-20 -15 All netmail areas, plus areas 10..20, except area #15 Note: Since ProBoard parses only the first letter of an alpha area selection, the keywords from prior versions, [Local / Net / Echo] can still be used and will still work. It is recommended however, that you change to the new 1.21 parameter(s) since the keywords [Local / Net / Echo] may not be supported in upcoming versions. ┌──────────────────────────────────────────────────────────────────┐ │ Function 50: SHOW USERS ONLINE │ └──────────────────────────────────────────────────────────────────┘ DATA: - Displays who is online on the other nodes. Of course, you understand that this function is useful only on multi-user systems. To protect the Sysop's health, it is possible not to show the Sysop's name here (Refer to the ProCFG section). - 84 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 51: LIST LAST CALLERS │ └──────────────────────────────────────────────────────────────────┘ DATA: <number of users to be displayed> Gives an overview of the users that have most recently logged in (for ALL the nodes). In the non-registered version, the number of users shown is forced to 5. ┌──────────────────────────────────────────────────────────────────┐ │ Function 52: REMOTE USER EDITOR │ └──────────────────────────────────────────────────────────────────┘ DATA: - Allows you to adjust a user's level (or even delete him), without you having to be at the computer (VERY handy for co-Sysops!). ┌──────────────────────────────────────────────────────────────────┐ │ Function 53: MULTILINE CHAT (INTERNODE CHAT) │ └──────────────────────────────────────────────────────────────────┘ DATA: - This is certainly the nicest function in ProBoard! This function allows two users on different nodes to chat with each other IN REAL TIME!!! You will actually see the other user type (mistakes?), as if you were in chat-mode with the Sysop. This is UNlike other systems, where entire LINES are sent to the other node. User A on node X will have to specify the node he wants to chat with, whereafter user B on node Y will be prompted if he wants to chat. It is VERY (!VERY!) important that your system supports full file & record locking to use this option. When you are not running a LAN, you MUST install SHARE.EXE! ProBoard will definitely lock up when SHARE.EXE is not installed on a stand-alone system. - 85 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 54: SELECT FILE AREA │ └──────────────────────────────────────────────────────────────────┘ DATA: <area selection> Lets the user select a new file area. This function is to be used in cooperation with other file-related functions. Refer to functions 1 and 32 for more information. ┌──────────────────────────────────────────────────────────────────┐ │ Function 55: SHOW .GIF FILE INFO │ └──────────────────────────────────────────────────────────────────┘ DATA: <area selection> Prompts the user for a .GIF-filename (wildcards allowed) and displays resolution and number of colors for the file(s). The files will be looked for in <area selection>. Refer to function 32 (Download) for more information. ┌──────────────────────────────────────────────────────────────────┐ │ Function 56: TOGGLE IBM CHARACTERS │ └──────────────────────────────────────────────────────────────────┘ DATA: - Allows the user to disable/enable extended IBM characters. When disabled, all IBM-specific characters are converted to standard ASCII characters ("+-|") ┌──────────────────────────────────────────────────────────────────┐ │ Function 57: CHANGE PHONE NUMBER │ └──────────────────────────────────────────────────────────────────┘ DATA: - Allows the user to change his phone number stored in his user record. - 86 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 58: CHANGE DATA/FAX PHONE NUMBER │ └──────────────────────────────────────────────────────────────────┘ DATA: - Allows the user to change his data/fax phone number stored in his user record. ┌──────────────────────────────────────────────────────────────────┐ │ Function 59: CHANGE USER ALIAS │ └──────────────────────────────────────────────────────────────────┘ DATA: - Allows the user to change his alias. It is not allowed to use an alias that is being used by another user. ┌──────────────────────────────────────────────────────────────────┐ │ Function 60: RUN PROBOARD SDK FILE │ └──────────────────────────────────────────────────────────────────┘ DATA: <program> [data] Loads & executes a ProBoard Executable (PEX file) created using the ProBoard Software Development Kit (SDK). The PEX file must reside in the PEX-directory (Specified in ProCFG). - 87 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 61: BULLETIN MENU │ └──────────────────────────────────────────────────────────────────┘ DATA: <filename> [prompt] Displays <filename>.ANS/ASC (like function 5), and prompts the user for a file suffix. This suffix is appended to <filename>, and the file with the resulting filename is displayed. Obviously, <filename> should not be longer than 7 characters. The optional [prompt] parameters defines a prompt to be shown to the user. For example: Enter a bulletin. Data example: BULLET Enter a bulletin: ┌──────────────────────────────────────────────────────────────────┐ │ Function 62: TOGGLE AVATAR/0 │ └──────────────────────────────────────────────────────────────────┘ DATA: <blank> or <parameter> Allows the user to toggle AVATAR/0 on/off in their user record. In the data field, you can enter these parameters: Ask Will ask for new status On Toggles option on Off Toggles option off Toggle Toggles option (reverse of current condition) Save Save current status for this option Restore Restore status saved by "Save" /Q Quiet. Do not display "xxxx is now enabled/disabled" Example: "Ask /Q" This will ask the user if they want to enable or disable AVATAR/0 screen display codes, and ProBoard will not display: "Avatar codes are now enabled/disabled". "Toggle" parameter. - 88 - ┌──────────────────────────────────────────────────────────────────┐ │ Function 63: TOGGLE AVATAR/0+ │ └──────────────────────────────────────────────────────────────────┘ DATA: <blank> or <parameter> Allows the user to toggle AVATAR/0+ on/off in their user record. In the data field, you can enter these parameters: Ask Will ask for new status On Toggles option on Off Toggles option off Toggle Toggles option (reverse of current condition) Save Save current status for this option Restore Restore status saved by "Save" /Q Quiet. Do not display "xxxx is now enabled/disabled" Example: "Ask /Q" This will ask the user if they want to enable or disable AVATAR/0+ screen display codes, and ProBoard will not display: "AVT/0+ codes are now enabled/disabled". "Toggle" parameter. - 89 - ╒══════════════════════════════════════════════════════════════════╕ │░░░░░░ USERS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════════╛ The file USERS.BBS contains all the data about the users, such as level, number of times called, combined boards access, messages last read, etc. Use ProBoard's User Editor to add/edit/delete users in the USERS.BBS file. If you delete users you must run PBUTIL [UK]. More info on this in the section on PBUTIL. ┌──────────────────────────────────────────────────────────────────┐ │ Log Levels │ └──────────────────────────────────────────────────────────────────┘ Each user has a certain loglevel, to determine how information about that user will be written to ProBoard's log (PROBOARD.LOG). This can be useful if you suspect a user of logging in using 2 different names. If you give those users a higher log level, you can track their behaviour. The following levels are possible: Friend * NOTHING BUT login, logoff and errors will be logged. Normal * Login * Logoff * Errors * Writing Sysop messages * Sysop paging * Downloads * Uploads * Questionnaires Suspicious * Everything from 'Normal' * Reading messages * Hitparades * Last callers * Graphics Dangerous * Everything from 'Suspicious' * ALL the movements between menus (this can make the logfile HUGE) - 90 - ╒══════════════════════════════════════════════════════════════════╕ │░░░░░░ ECHOMAIL & NETMAIL ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════════╛ ProBoard fully supports Echomail and Netmail, according to the FTSC (FidoNet Technical Standards Committee) specifications. ┌──────────────────────────────────────────────────────────────────┐ │ Echomail │ └──────────────────────────────────────────────────────────────────┘ When a user enters a message in a message area configured as an Echomail area, an origin line will be added to that message. This origin line is obtained from the message area's configuration. If there is no origin line specified for this message area, the default origin line will be used. The default origin line is specified in PROCFG under Options (F1) - Site Info, in the field "Default Origin Line". To import/export Echomail, you need an Echomail processor. No such program is included, but as ProBoard uses the Hudson message-base structure, a large number of Echomail processors are available. Great echomail-processors compatible with ProBoard are: - QEcho - ZmailH - TosScan - GECHO ┌──────────────────────────────────────────────────────────────────┐ │ Netmail │ └──────────────────────────────────────────────────────────────────┘ A Netmail message (in short: Netmail) is a message that has a fixed destination within the network. This destination is defined by a node-number of the form "Zone:Net/Node.Point". ProBoard will first find out whether this address exists, and will then (if it exists) tell you the name of the node where the Netmail is to be sent to. When entering a node number in ProBoard, it is possible to look up the nodes you want by entering a '?'. - 91 - eg: ? Shows a list of all zones. 2:? Shows a list of all nets and regions in zone 2. 2:292/? Shows a list of all nodes in net 2:292/ ProBoard needs a nodelist to use Netmail. This nodelist is usually available on every node in the network. ProBoard generates an index file for its own use (NODE_IDX.PRO) by running PBUTIL NC. For more information about PBUTIL's NC-option, please refer to the section on PBUTIL. To import and export Netmail, you need an external utility like MAILSCAN ,MBUTIL or ZmailH. - 92 - ╒═════════════════════════════════════════════════════════════════╕ │░░░░░░ PBUTIL ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘═════════════════════════════════════════════════════════════════╛ PBUtil is an extra utility provided with the ProBoard package. It performs all of the maintenance your ProBoard system needs. PBUtil is called with a parameter specifying the operation to be executed: PBUTIL <operation> [option] Operations: MP Message Packer MI Message Indexer ML Message Linker UF Userfile Fixer UP Userfile Packer UK User Killer UI Userfile Indexer FC File Counters NC Nodelist Compiler MU Music player PBUtil can be run from any directory provided that it (PBUTIL) is found in your DOS path. Refer to your DOS manual for more information on the PATH statement. - 93 - ┌──────────────────────────────────────────────────────────────────┐ │ [MP] Message Packer │ └──────────────────────────────────────────────────────────────────┘ Packs the message base. This means that the deleted messages are effectively removed from the message base. Specifying option -R will instruct the message packer to renumber the message base. Renumbering the message base is done automatically when the highest message number exceeds 25000. Option -F forces the pack to be executed, even if there are no deleted messages. Option -K will delete the .BAK files created when packing the message base. Option -D will remove old messages. Check the section about the message areas for more information. Lastread-pointers in the userfile will be adjusted when renumbering. Do NOT pack the messagebase when a user is online!! ─────────────────────────────────────────────────── ┌──────────────────────────────────────────────────────────────────┐ │ [MI] Message Indexer │ └──────────────────────────────────────────────────────────────────┘ Recreates the message base index files. (MSGIDX.BBS,MSGTOIDX.BBS and MSGINFO.BBS). ┌──────────────────────────────────────────────────────────────────┐ │ [ML] Message Linker │ └──────────────────────────────────────────────────────────────────┘ Completely rebuilds reply chains in all areas. This operation has to be performed when echomail is imported into the message base and after using the message packer with the -D parameter. - 94 - ┌──────────────────────────────────────────────────────────────────┐ │ [UP] UserFile Packer │ └──────────────────────────────────────────────────────────────────┘ Removes all deleted users from USERS.BBS, except the users with the NoKill flag set. Corrupted user records are also removed. Specifying option -R instructs the user packer to reset all Last Read pointers to zero. Specifying option -K will delete the .BAK file created when packing the user file. Do NOT pack the userfile when a user is online!! ──────────────────────────────────────────────── ┌──────────────────────────────────────────────────────────────────┐ │ [UI] UserFile Indexer │ └──────────────────────────────────────────────────────────────────┘ Creates an index for the user file. ProBoard uses this index file to search in the user file. This greatly reduces the time needed to locate a user at login. ┌──────────────────────────────────────────────────────────────────┐ │ [UF] UserFile Fixer │ └──────────────────────────────────────────────────────────────────┘ Run this after you use a user file packer/sorter from another source (like RAUSER or RACE). It assures that the extensions in ProBoard's user file are updated properly. - 95 - ┌──────────────────────────────────────────────────────────────────┐ │ [UK] UserFile Killer │ └──────────────────────────────────────────────────────────────────┘ Deletes (kills) certain users from USERS.BBS. The criteria are: not having called for a certain number of days, less than a certain number of times called, or a combination of these two. Parameters to use: -D<# of days> Removes all users that haven't called for <# of days>. -C<calls> Removes all users that have called less than <calls> times. Combining these two parameters, will remove all users that have called less than <calls> times and haven't called for <# of days>. This option comes in handy to remove all users that have called just once, but without removing your new users! Examples: PBUTIL UK -C3 Removes all users that have called only 1 or 2 times. PBUTIL UK -D365 Removes all users that haven't called for the last 365 days. PBUTIL UK -C2 -D100 Removes all users that have called less than 2 times, and removes users that haven't called in the last 100 days. "No-Kill" flags in User Records will be honored. - 96 - ┌──────────────────────────────────────────────────────────────────┐ │ [FC] File Counters │ └──────────────────────────────────────────────────────────────────┘ After each download, ProBoard adds a line to the file DOWNLOAD.LOG. This file's only purpose is to be used by the FC module of PBUtil. FC reads the file DOWNLOAD.LOG and updates file counters in every file listing, to keep up with the number of times every file has been downloaded. Specifying option -N<xx> instructs PBUtil to create a list of the top-xx downloaded files. This list is named TOPFILES.A?? and is stored in the textfiles-subdirectory. The number of files to be written in this list is <xx>, (eg. -N15). Specifying option -F instructs PBUtil to ALWAYS create TOPFILES.ASC/ANS/AVT/AVP, even if DOWNLOAD.LOG is empty or doesn't exist. Option -R rewrites all file listings with the appropriate file count added to each file. This is useful when you have added some new files. The file counters will be placed before the description of the files. Eg. PB_121.ARJ [89] Superb new BBS program from Belgium !!!! ^^^^ File Counter - shows how many times file has been downloaded. You can create a file called NOTOPS.CTL to exclude files from being included when the TOPFILES.A?? is created. The format of this file is just <filename>.<extension> Example as follows: BLACK.ZIP NOWAY.EXE RA_111.ARJ ┌──────────────────────────────────────────────────────────────────┐ │ [NC] Nodelist Compiler │ └──────────────────────────────────────────────────────────────────┘ Reads a FidoNet-compatible nodelist and creates a ProBoard index- file (NODE_IDX.PRO) in the system directory. This file will be less than 10K in size, but your original nodelist has to stay in the nodelist directory. - 97 - The compiler will look for the latest standard nodelist (NODELIST.xxx) in your nodelist directory. Specifying extra files as parameters instructs the nodelist compiler to compile extra nodelists. Several extra nodelists can be given as parameters. If you don't specify an extension, ProBoard will look for the latest file with extension .nnn (nnn=day number). If you want to compile a file without an extension, use <FILE>. Eg. PBUTIL NC MYNL MYLIST. FDNET.PVT This would compile the latest NODELIST.nnn, the latest MYNL.nnn, MYLIST and FDNET.PVT in the standard nodelist directory. To determine the costs of sending Netmail, a textfile will be read that you will have to create. This textfile is called COST.PRO and should be in ProBoard's system directory. The lines in this file have the following format: <Command> <Param1> [Param2] Commands: MYZONE <zone> All commands after this command act on zone <zone>. You need at least 1 MYZONE command. If not, ProBoard will assume you are in zone 2. This is used to specify your own zone. DEFAULT <cost> Defines the default Netmail cost. ZONE <zone> <cost> Defines the Netmail cost for zone <zone>. REGION <region> <cost> Defines the Netmail cost for region <region> within your own zone. NET <net> <cost> Defines the Netmail cost for net <net> within your own zone. - 98 - A simple example for a node in Belgium, where the BBS is part of only ONE network. MYZONE 2 I'm in zone 2 DEFAULT 100 Default = 100 credits ZONE 3 50 Zone 3 = 50 credits (Australia) ZONE 1 40 Zone 1 = 40 credits (North-America) REGION 28 10 Region 28 = 10 credits (Netherlands) REGION 29 0 Region 29 = FREE (Belgium) NET 512 5 Net 512 = 5 (HCC Netherlands) We give another example for a node which is part of 2 networks, so this node has nodenumbers 2:292/1900 and 89:120/40 DEFAULT 100 Default = 100 credits ZONE 1 50 Zone 1 = 50 credits ZONE 2 20 Zone 2 = 20 credits ZONE 3 70 Zone 4 = 70 credits ZONE 89 10 My private network = 10 credits MYZONE 2 Following definitions are for zone 2 REGION 29 1 Region 29 in zone 2 = 1 credit NET 292 0 Net 292 in zone 2 = 0 credits NET 512 5 Net 512 in zone 2 = 5 credits MYZONE 89 Following definitions are for zone 89 REGION 12 2 Region 12 in zone 89 = 2 credits NET 120 0 Net 120 in zone 89 = 0 credits ┌──────────────────────────────────────────────────────────────────┐ │ [MU] Music Player │ └──────────────────────────────────────────────────────────────────┘ Use this to play/test any music files you create for ProBoard. Music files MUST have .MUS as the file extension. The file played when a user "Yells" for the Sysop (paging) is called PAGE.MUS and the "Attention" music file is called ATTEN.MUS Examples: PBUTIL PAGE (plays the paging music file) PBUTIL ATTEN (plays the attention music file) PBUTIL MU to play a music file. - 99 - ╒══════════════════════════════════════════════════════════════════╕ │░░░░░░ REFERENCE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════════╛ ┌──────────────────────────────────────────────────────────────────┐ │ Multi-user Operation │ └──────────────────────────────────────────────────────────────────┘ Since ProBoard is a multi-line BBS package, it allows you the ability to have more than one user use the userfile and the message base at the same time. ProBoard doesn't do any internal multi-tasking to make the program act as flexible as possible. This makes sure that you can set up a multi-line BBS via a network and multiple computers, or by running ProBoard under a multitasking system. ProBoard has some code built in to run it as efficiently as possible under DESQview. It is also compatible with the new multitasking version of DR-DOS. ProBoard can handle up to 255 nodes. Each node needs its own directory, because ProBoard supports the use of an external message editor. These editors were designed to be used on single-node systems. Each node MUST be started from its own private directory. No ProBoard-related files have to be placed in this directory (only the files needed for the external message editor). If you want to install 3 nodes in a network, you could create the following structure: C:\PB\MSGBASE Message base directory C:\PB\TXTFILES Textfiles directory C:\PB\MENUS Menus directory C:\PB\PEX PEX files directory C:\PB\NODE1 Start-up directory for node 1 C:\PB\NODE2 Start-up directory for node 2 C:\PB\NODE3 Start-up directory for node 3 - 100 - ProBoard should be started from C:\PB\NODE1 for node 1, from C:\PB\NODE2 for node 2, etc. These directories only require the files for the external editor. All the other files that ProBoard uses, should be stored in ProBoard's system directory (usually C:\PB). If you run ProBoard under a multitasker like DESQview, the different nodes MUST be run on different com-ports. ┌───────────┬────────────────────────────────────────────────────┐ │ IMPORTANT │ If you are running ProBoard multi-line using a │ ├───────────┘ multitasker, the DOS program SHARE.EXE MUST! be │ │ installed. ──── │ └────────────────────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────┐ │ Sysop Keys │ └──────────────────────────────────────────────────────────────────┘ While the user is on-line, the Sysop can perform several actions, by using the Sysop keys: Left/Right Lower/Raise the current user's level. Only the levels configured in PROCFG can be selected. Up/Down Raise/Lower the current user's time left. The time subtracted/added is not restricted to this session! Alt-C [Chat] Start a chat with the user. The chat may be ended by pressing <Esc>. Alt-J [Jump] Jump to DOS. If 'Swapping' was set to 'Yes' in PROCFG, the ProBoard session will be swapped to disk or EMS, thus making all memory available to the DOS commands you want to execute. You can return from the shell by entering EXIT at the DOS prompt. Alt-H [HangUp] Hangs up the phone, throwing the user off-line immediately (very unfriendly)! - 101 - Alt-L [LockOut] Hangs up the phone AND sets the user's level to 0, thus making sure he/she cannot log in any more (very very unfriendly)! Alt-N [NoChat] Makes ProBoard shut up during this session. Comes in VERY handy when you see the user-that-ALWAYS-wants-to-chat is logging in. Alt-E [Edit] Allows you to edit the user online. The editor is similar to the editor in ProCFG. Alt-I [Image] Appends an image of the screen to the file IMAGE.TXT in the ProBoard system directory. Alt-R [Reset] Resets the chat request status. This will stop the flashing of the status line. Alt-S [Static] What can I say. Useful in combination with the ALT-H to help you, the friendly Sysop, free up your board when needed. (somewhat friendlier) ;-) Shift-F1 Shows a help-screen with all the Sysop macros available. (registered version only) F1 Shows a help-screen with all the Sysop keys available. PgUp/PgDn Shows additional information about the current user on the status line. You can also display a particular status by pressing F2-F10. Home Shows the normal status line after using PgUp/PgDn. F2 Shows the user's name, level, time left and time online. F3 Shows the user's handle and flags. - 102 - F4 Shows the user's city and phone numbers. F5 Shows statistics about the current user. F6 Shows the user's comment line. F7 Shows system information. F8 Shows the chat reason if the user tried to page the Sysop earlier. F9 Shows the name and login time of the last caller. F10 Shows the time used and Kbytes downloaded today. It also displays the date of birth of the current user. Furthermore, there are 10 programmable hotkeys (Sysop macros). They can be configured in ProCFG. There are 2 kinds of Sysop macros: - Key macros : With this type of macro, it is possible to assign many keystrokes to a single key. When the macro key is pressed, all keys specified will be passed to ProBoard, as if you typed them yourself. Special chars: '|' is replaced by <Enter> '^' is replaced by <Esc> - Shell macros : You can link any DOS command to a macro's hot- key. A shell-definition MUST start with a '@'. The string following the '@' should contain the DOS command to be executed. You can, of course, use the special shell options from menu function 7. Take this for an example: Suppose you have set 'Swapping' to 'No' in ProCFG. Should you, however, need ALL your system memory in the shell, you could define the following macro: @*C*N*Q*X (COMMAND.COM, NoLog, NoMsg, Swapping). - 103 - ┌──────────────────────────────────────────────────────────────────┐ │ Command line parameters & Errorlevels │ └──────────────────────────────────────────────────────────────────┘ PROBOARD.EXE accepts following command line parameters: PROBOARD [-B<baud>] [-P<port>] [-N<node>] [-L<level] - 104 - [-T<time>] [-S] [-Q] [-X] [-V<mode>] These parameters have the following meaning: -B<baud> Specifies the baud rate. You can specify the following baud rates: 300, 1200, 2400, 4800, 7200, 9600, 12000, 14400, 19200 and 38400. -P<port> Specifies the com-port (1-8). -N<node> This node's node number (1-255). -L<level> Prevents people with a security level lower than this level to access this node. Great for only allowing subscribing user access to one or more nodes. -T<time> <time> is the time until the next event in minutes. Useful with FrontDoor's DOBBS batch file. -S Start ProBoard in stand alone mode. ProBoard will use as a default the PORT and the BAUD specified in your configuration, but you can override them by using the -P<port> and the -B<baud> command line parameters along with the -S parameter. -Q Quiet mode. Great if your BBS is in a location such as your bedroom etc. The only noise ProBoard will make is playing the ATTEN.MUS file (if a user who has this set in their user record logs on), and playing the PAGE tune when a user pages during valid paging hours. -X Tells ProBoard not to use EMS. -V<mode> Runs ProBoard in video mode <mode>. This can be useful if you have a monitor capable of displaying 132 columns, and you would like to run ProBoard in such a mode (you will see an extra information window on your screen if ProBoard is run in 132 cols mode). The <mode> parameter is a decimal number specifying the video mode, as it is used with INT 10H, function 00. (only programmers will understand this though :-) When no '-B<x>' and no '-S' parameter is given, ProBoard will be started in local mode. - 105 - ProBoard returns an errorlevel when a user has logged off. The errorlevels of PROBOARD.EXE are: 0 Everything OK, normal logoff. 1 FATAL error, something 'terrible' happened, or the modem could not be initialized. 2 Not used. 3 Netmail entered by the user. 4 Echomail entered by the user. 5 Echomail AND Netmail entered by the user. 99 Sysop pressed <Esc> at the "Waiting for call" screen. - 106 - ┌──────────────────────────────────────────────────────────────────┐ │ AVATAR/0 and AVATAR/0+ Terminal Emulation │ └──────────────────────────────────────────────────────────────────┘ ProBoard now supports AVATAR terminal emulation. It allows users to select either AVATAR/0 or AVATAR/0+, providing that the terminal package they use to call your BBS is compatibile with either AVATAR/0 and/or AVATAR/0+. Examples of terminal software packages that support AVATAR/0+ are, FrontDoor 2.02 and TinyTerm. QModem and Telix also support AVATAR, but only in the AVATAR/0 mode. AVATAR has the advantage over ANSI of being much faster. A word about the files extensions (.A??) that are used for AVATAR screens. There are two file extensions that are associated with AVATAR text files that you will display to your users. They are .AVT and .AVP. When displaying (.A??) textfiles to your users, ProBoard looks for them in the following order. 1.) .AVP 2.) .AVT 3.) .ANS 4.) .ASC Refer to the following section on "Hard Coded .A?? files" for more information on the default .A?? files that ProBoard will display to your users. To create files with the .AVT and .AVP file extensions you will need a file utility called AVTCONV.EXE. This file was distributed with RemoteAccess, and is also available from most of the ProBoard beta sites, as well as any of the ProBoard Support BBS's. It is very simple to use this utility. Just copy it to your ProBoard TEXTFILE directory and run the following commands. AVTCONV *.ANS AVT -- this will create a copy of all of your ANSI (.ANS) screens with the extension .AVT These are the textfiles for displaying to users that have AVATAR/0 terminal emulation selected. AVTCONV /C+ *.ANS AVP -- this will create a copy of all of your ANSI (.ANS) screens with the extension .AVP These are the textfiles for displaying to users that have AVATAR/0+ terminal emulation selected. - 107 - ┌──────────────────────────────────────────────────────────────────┐ │ Hard-coded .A?? files │ └──────────────────────────────────────────────────────────────────┘ In certain situations, ProBoard will display default .A?? files. .A?? files are defined as files that have the file extensions of .AVT, .AVP, .ANS, and .ASC. If the .ANS/AVT/AVP file cannot be found, the .ASC file will be displayed (if it exists). Note: You have to insert your own "Press [Enter] to continue" prompt if necessary! INTRO.A?? Displayed when a user logs in, BEFORE asking a user's name and password. GOODBYE.A?? Displayed when the user is logging off, just before the carrier is dropped. NEWUSER1.A?? Displayed when a new user is logging in, BEFORE he/she has started the questionnaire. NEWUSER2.A?? Displayed when a new user is logging in, AFTER he/she has completed the questionnaire. WELCOMEx.A?? Displayed at login, after the user entered his/her name. The 'x' stands for a digit ranging from 1 to 9; these files (if they xist) will be displayed in ascending order, 1-2-...-9, BEFORE a mailcheck is done. NEWS.A?? Displayed AFTER the user has read his/her new mail. SECxx.A?? 'xx' stands for a userlevel. If a user with level xx logs in, this file will be displayed (eg. SEC25.ANS). The file is shown after all WELCOME<x> files and before the mailcheck. MAXPAGE.A?? Displayed when the user has tried to page the Sysop too many times. PAGED.A?? Displayed when the Sysop does not respond when the user tries to page. NOTAVAIL.A?? Displayed when the user tries to page outside paging hours. - 108 - MSGHELP.A?? Replaces the built-in message reading help if this file exists. PRIVATE.A?? Is displayed when your system is configured as a private system, and a new user tries to log in. EXP_WARN.A?? Displayed when the user's level expires within less than 30 days. EXPIRED.A?? When a user's level has expired, this file is shown. TRASHCAN.A?? Shown when a user tries to use a name listed in TRASHCAN.CTL file. EVENTDUE.A?? Shown if a user can't login because of an event that has to run soon. BIRTHDAY.A?? If a user logs in on his/her birthday, this file will be shown after the news file. Note: you can run a pex-file to congratulate a user on his/her birthday. DLDELAY.A?? Displayed to a user who has to wait <n> minutes before downloading. Refer to Configuration - Time/DownLoad Limits (F5) for more information on setting the number of minutes for the DownLoad Delay. DLHANGUP.A?? Displayed to a user who has selected [G]oodbye after download, after the 10 second timer to abort the hangup, has expired. - 109 - ┌──────────────────────────────────────────────────────────────────┐ │ .A?? File Control Codes │ └──────────────────────────────────────────────────────────────────┘ You can use several codes in ProBoard's textfiles. These codes will be replaced by internal variables, or will perform special actions. In the code list, you will see a code's ASCII value, the control code and a description of the code. A '^' means Ctrl, so ^D means Ctrl-D. ┌───────┬──────┬─────────────────────────────────────────────────┐ │ ASCII │ CODE │ DESCRIPTION │ ├───────┼──────┼─────────────────────────────────────────────────┤ │ 65 │ ^A │ Waits for the user to press <Enter>. │ │ 66 │ ^B │ Disables interruption by pressing <S>. │ │ 67 │ ^C │ Enables interruption by pressing <S>. │ │ 68 │ ^D │ Enables 'More'-prompt. │ │ 69 │ ^E │ Disables 'More'-prompt. │ │ 71 │ ^G │ Rings a bell on the user's computer. │ │ 76 │ ^L │ Clearscreen. │ │ 87 │ ^W │ Pauses for 1 second. │ └───────┴──────┴─────────────────────────────────────────────────┘ - 110 - ┌───────┬──────┬─────────────────────────────────────────────────┐ │ ASCII │ CODE │ DESCRIPTION │ ├───────┼──────┼─────────────────────────────────────────────────┤ │ 06-65 │ ^FA │ User's full name. │ │ 06-66 │ ^FB │ User's City. │ │ 06-67 │ ^FC │ User's password. │ │ 06-68 │ ^FD │ User's data/fax phone number. │ │ 06-69 │ ^FE │ User's phone number. │ │ 06-71 │ ^FG │ Time of last login. │ │ 06-76 │ ^FL │ Netmail credit left. │ │ 06-77 │ ^FM │ Number of messages written. │ │ 06-78 │ ^FN │ Message last read. │ │ 06-79 │ ^FO │ User's level. │ │ 06-80 │ ^FP │ Number of calls by user. │ │ 06-81 │ ^FQ │ Number of uploads by user. │ │ 06-82 │ ^FR │ Kbytes uploaded by user. │ │ 06-83 │ ^FS │ Number of downloads by user. │ │ 06-84 │ ^FT │ Kbytes downloaded by user. │ │ 06-85 │ ^FU │ Number of minutes online today. │ │ 06-86 │ ^FV │ User's screen length. │ │ 06-87 │ ^FW │ User's first name. │ │ 06-88 │ ^FX │ ANSI codes ON/OFF. │ │ 06-89 │ ^FY │ Screen pausing ON/OFF. │ │ 06-90 │ ^FZ │ Clearscreen codes ON/OFF. │ │ 06-48 │ ^F0 │ Fullscreen editor ON/OFF. │ │ 06-49 │ ^F1 │ User's Alias. │ │ 06-50 │ ^F2 │ Command stacking ON/OFF. │ │ 06-51 │ ^F3 │ IBM Characters ON/OFF. │ │ 06-52 │ ^F4 │ User's country. │ │ 06-53 │ ^F5 │ User's birth date. │ │ 06-54 │ ^F6 │ User's expiration date (if any) │ │ 06-55 │ ^F7 │ Day's until expiration date. │ │ 06-56 │ ^F8 │ AVATAR/0 - on/off. │ │ 06-57 │ ^F9 │ AVATAR/0+ - on/off. │ │ 06-91 │ ^F[ │ Download Kb left today. │ │ 06-126│ ^F~ │ Download delay in minutes. │ │ 06-33 │ ^F! │ # Minutes remaining until allowed to download. │ └───────┴──────┴─────────────────────────────────────────────────┘ - 111 - ┌───────┬──────┬─────────────────────────────────────────────────┐ │ ASCII │ CODE │ DESCRIPTION │ ├───────┼──────┼─────────────────────────────────────────────────┤ │ 11-65 │ ^KA │ Total number of calls to the BBS. │ │ 11-66 │ ^KB │ Name of the last user on the BBS. │ │ 11-67 │ ^KC │ Number of active messages. │ │ 11-68 │ ^KD │ Number of first message. │ │ 11-69 │ ^KE │ Number of last message. │ │ 11-70 │ ^KF │ Number of times user has paged the Sysop. │ │ 11-71 │ ^KG │ Day of the week (full). │ │ 11-72 │ ^KH │ Number of users on the BBS. │ │ 11-73 │ ^KI │ Current time. │ │ 11-74 │ ^KJ │ Today's date. │ │ 11-75 │ ^KK │ Minutes online during this session. │ │ 11-77 │ ^KM │ Minutes online today. │ │ 11-79 │ ^KO │ Minutes online left today. │ │ 11-80 │ ^KP │ Version number of ProBoard (x.xx) │ │ 11-81 │ ^KQ │ Daily online limit. │ │ 11-82 │ ^KR │ Baud rate. │ │ 11-83 │ ^KS │ Day of the week (short). │ │ 11-84 │ ^KT │ Daily download limit (Kbytes). │ │ 11-87 │ ^KW │ Node number. │ │ 11-88 │ ^KX │ Hang up phone. │ │ 11-89 │ ^KY │ Active message area name. │ │ 11-90 │ ^KZ │ Active file area name. │ │ 11-48 │ ^K0 │ # Messages in active message area │ │ 11-49 │ ^K1 │ Current message area # │ │ 11-50 │ ^K2 │ Current file area # │ └───────┴──────┴─────────────────────────────────────────────────┘ You can also inform ProBoard about the length of a string to be placed in a textfile. This is done is the following way: Between the first and last code, you can place '@' or '#' codes. The field's length will be defined by the number of characters, first and last control code included. Use '@' to align (justify) a field to the left, use '#' to align to the right. Eg. ^K@@@@@@@@@@@@@@@@@@@@@@@B ^^^^^^^^^^^^^^^^^^^^^^^ 23 X '@' Thus, the total amount of characters equals 25, the user's name (^KB) will be placed in a 25-character field, left justified. You now can easily draw 'boxes' around this field, without having to worry about the actual length of the user's name. - 112 - An example of a textfile using the control codes: (the '^' stands for '^F') : ┌───────────┐ │ Some Info │ └───┬───────┴───────────────────────────────────────────────────┐ │ Your full name..... ^@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@A │ │ Calling from....... ^@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@B │ │ Last called........ ^@@@@@@@@@F at ^@@@@@@G │ │ Level.............. ^####O │ │ Number of calls.... ^####P │ ├──────────────────────────────┬────────────────────────────┤ │ Kb downloaded...... ^@@@@TK │ Kb uploaded....... ^####RK │ │ # downloads........ ^####S │ # uploads......... ^####Q │ ├──────────────────────────────┴────────────────────────────┤ │ Messages posted.... ^####M │ │ Your flags......... ^@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@H │ ├─────────────────┐ │ │ ANSI ^#X ├─────────────────────────────────────────┘ │ Clearscreen ^#Z │ │ More prompt ^#Y │ │ Editor ^#O │ └─────────────────┘ Press <Enter> to continue.^A ┌──────────────────────────────────────────────────────────────────┐ │ Music Files │ └──────────────────────────────────────────────────────────────────┘ You can make your paging-sound and attention-sound more attractive by defining your own musicfile. A musicfile is a text file in which you can use 2 keywords: TONE [hz] [1/100's sec] Sounds a tone of [hz] Hz during the specified period. WAIT [1/100's sec] Waits for the specified period. The format of this textfile is compatible with the RemoteAccess musicfiles. The paging-musicfile is named PAGE.MUS, and the attention-music- file is named ATTEN.MUS. - 113 - You can use this frequency-table to write your own masterpiece: ┌──────┬─────┬─────┬──────┬──────┬──────┐ │ O.1 │ O.2 │ O.3 │ O.4 │ O.5 │ O.6 │ ┌────┼──────┼─────┼─────┼──────┼──────┼──────┤ │ C │ 45 │ 134 │ 268 │ 536 │ 1071 │ 2145 │ │ C# │ 71 │ 142 │ 284 │ 568 │ 1136 │ 2273 │ │ D │ 75 │ 150 │ 301 │ 602 │ 1204 │ 2408 │ │ D# │ 80 │ 159 │ 319 │ 638 │ 1275 │ 2551 │ │ E │ 84 │ 169 │ 338 │ 676 │ 1351 │ 2703 │ │ F │ 90 │ 179 │ 358 │ 716 │ 1432 │ 2864 │ │ F# │ 95 │ 190 │ 379 │ 758 │ 1517 │ 3034 │ │ G │ 100 │ 201 │ 402 │ 804 │ 1607 │ 3215 │ │ G# │ 106 │ 213 │ 426 │ 851 │ 1703 │ 3406 │ │ A │ 113 │ 225 │ 451 │ 902 │ 1804 │ 3608 │ │ A# │ 119 │ 239 │ 478 │ 956 │ 1991 │ 3823 │ │ B │ 127 │ 253 │ 506 │ 1012 │ 2025 │ 4050 │ └────┴──────┴─────┴─────┴──────┴──────┴──────┘ ┌──────────────────────────────────────────────────────────────────┐ │ Text Macros │ └──────────────────────────────────────────────────────────────────┘ You can enter text macros in any user-definable string. Text macros are defined as "@<NAME:n>@", and are replaced by internal ProBoard variables at runtime. You can insert these macros in the following strings: - Textlines in menu items - Data fields in menu items - Menu prompts - "Yelling" message for Menu Function 11 - "Shelling" message for Menu Function 7 - Modem initialization string 'NAME' is the name of the macro. A list of available macros will follow. You can also specify the field width for the resulting string. This is done by appending the macro name with a ':' and a number. A positive number will result in a left aligned string, while a negative number will result in a right aligned string. For example: @<NAME:30>@ will display the user's name in a left aligned field of 30 characters wide. Note that the field width specifier is optional. - 114 - Here is a list of the available macros: BAUD Current baud rate CITY The city of the current user COUNTRY User's country/state CURFILEAREA Current file area name CURFILEAREA# Current file area number CURMENU Current menu name CURMSGAREA Current message area name CURMSGAREA# Current message area number DATAPHONE User's data phone number DATE Current date (xx-xxx-xx) FIRSTNAME The first name of the current user HANDLE The user's handle (fixed alias) HIGHMSG Highest message number in message base ID The user level ID for this user LASTDATE Date of user's last call LASTTIME Time of user's last call LEVEL The level of the current user LOWMSG Lowest message number in message base MNUDIR Menu directory MSGDIR Messagebase directory NAME The name of the current user NLDIR Nodelist directory NODE Current node number NUMMSG Number of messages in current area NUMUSERS Total number of users in userfile NUMYELLS The number of times the user yelled PASSWORD The user's password PEXDIR PEX-files directory PORT Current com-port nr (1-8) PVTDIR Private uploads directory STARTDIR Startup-directory SYSDIR ProBoard system directory SYSOPNAME Name of the Sysop TIME Current time (xx:xx) TMLEFT Number of minutes left TMONLINE Number of minutes online TOTALCALLS Total number of calls to the system TOTALMSG Total number of messages in message base TXTDIR Textfiles directory UPDIR Upload directory USERREC Record number of this user's user record VERSION ProBoard version number (eg 1.21) VOICEPHONE User's voice phone number - 115 - %NAME Will be replaced by the contents of DOS environment variable 'NAME'. Example: in DOS or a .BAT file you would put SET INITSTR=ATDT5551212. Then when you use a text macro like this: @<%INITSTR>@ it would be replaced with "ATDT5551212". Note the "%" symbol in the macro. Other special characters are: #1 - #7 Change color (only valid for displayable #B1 - #B7 strings). If a 'B' is in front of the color number, the "blink" attribute will be turned on. 1 = Red 2 = Green 3 = Yellow 4 = Blue 5 = Magenta 6 = Cyan 7 = White Example: Hi @<#3>@@<FIRSTNAME>@@<#7>@, how is the weather in @<CITY>@? Other single examples: @<NAME:35>@ @<TMONLINE:-5>@ @<CITY>@ - 116 - ┌──────────────────────────────────────────────────────────────────┐ │ Example Batch Files │ └──────────────────────────────────────────────────────────────────┘ This is an example for standalone-operation with 2 errorlevel events defined. Event 1 returns level 10, event 2 returns level 20. No echomail and netmail is used. ------------------------------------------------------------------ :Loop PROBOARD -S if errorlevel 99 goto End if errorlevel 20 goto Event2 if errorlevel 10 goto Event1 if errorlevel 1 goto FatalError goto Loop :Event1 echo Perform some actions echo -------------------- goto Loop :Event2 echo Perform some more actions echo ------------------------- goto Loop :FatalError echo FATAL ERROR - ProBoard Down :End ------------------------------------------------------------------ Using ProBoard with a frontend-mailer is a little more complicated. This is an example for use with FrontDoor. In this example FrontDoor uses the following errrolevels: 300 bps call : 50 1200 bps call : 51 2400 bps call : 52 Local call : 60 Mail received : 100 Exit : 150 - 117 - ------------------------------------------------------------------ SET FD=C:\FD :Loop cd \fd fd if errorlevel 150 goto End if errorlevel 100 goto MailRcv cd\pb if errorlevel 60 goto Local if errorlevel 52 goto Call2400 if errorlevel 51 goto Call1200 if errorlevel 50 goto Call300 :FatalErr echo FATAL ERROR goto End :Call300 proboard -b300 -p1 goto CheckPBErr :Call1200 proboard -b1200 -p1 goto CheckPBErr :Call2400 proboard -b2400 -p1 goto CheckPBErr :Local proboard :CheckPBErr if errorlevel 5 goto NetEcho if errorlevel 4 goto EchoEntered if errorlevel 3 goto NetEntered if errorlevel 1 goto FatalErr goto Loop :NetEcho REM ************************************ REM ** Export netmail & echomail here ** REM ************************************ Goto Loop - 118 - :NetEntered REM ************************************ REM ** Export netmail here ** REM ************************************ Goto Loop :EchoEntered REM ************************************ REM ** Export echomail here ** REM ************************************ Goto Loop :MailRcv REM ************************************ REM ** Unpack and Import mail here ** REM ************************************ Goto Loop :End ------------------------------------------------------------------ - 119 - ┌──────────────────────────────────────────────────────────────────┐ │ Flag Cross-Reference Chart │ └──────────────────────────────────────────────────────────────────┘ The following cross-reference chart will help you to easily determine which flags to use for your user records and menus using the ProBoard style (A-Z and 1-6) of flags. Note: The flag structures in ProBoard are actually no different than those in QuickBBS or RA, they are just expressed in a more "user friendly" format. ╔═══╦═══╤═══╤═══╤═══╤═══╤═══╤═══╤═══╕ ║ ║ 1 │ 2 │ 3 │ 4 │ 5 │ 6 │ 7 │ 8 │ ╠═══╬═══╧═══╧═══╧═══╧═══╧═══╧═══╧═══╛ ║ A ║ A B C D E F G H ╟───╢ ║ B ║ I J K L M N O P ╟───╢ ║ C ║ Q R S T U V W X ╟───╢ ║ D ║ Y Z 1 2 3 4 5 6 ╙───╜ A few flag examples follow: QuickBBS/RA ProBoard ─────────── ──────── A1 A C3 S D7 5 C8 X well.... you get the idea. - 120 - ┌──────────────────────────────────────────────────────────────────┐ │ FREE Files │ └──────────────────────────────────────────────────────────────────┘ Many Sysops have a master file list containing all the files available on their BBS for users to download, or perhaps some virus detection software that they would like to make available to their users without affecting their users download ratio. It is possible (in addition to marking entire file areas) to specify a list of files that users can download without ProBoard deducting the kilobyte amount of the download from their daily limit. To accomplish this, create a file called FREEFILE.CTL in the ProBoard system directory (usually C:\PB). Create this file with an ascii editor such as QEDIT. Each line in the file should contain the name (do not include the drive and path to the file) and extension of any files you want to make available for FREE. Wildcards are allowed. An example follows: PB_121.ARJ FILELIST.ZIP *.TXT SCANV86.ZIP PB_STRUC.* LIST.LZH - 121 - ╒═════════════════════════════════════════════════════════════════╕ │░░░░░░░ USER'S GUIDE TO PROBOARD ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘═════════════════════════════════════════════════════════════════╛ This chapter explains the use of ProBoard from the caller's perspective. ┌──────────────────────────────────────────────────────────────────┐ │ Navigating Through Menus │ └──────────────────────────────────────────────────────────────────┘ ProBoard has been created for the novice and experienced user. It supports Opus-like commands and RA/QBBS style hotkeys. Using hotkeys is the easiest way to navigate through the menus. While a menu is being displayed, you can enter any menu command. The displaying of the menu will be stopped, and the corresponding menu function will be executed immediately. The other way to enter menu options is command stacking. This way you can enter several menu commands at a prompt, and execute them all at once by pressing [Enter]. You are not limited to menu commands only. You can enter any key that should be "stacked". A ';' stands for <Enter>. This asks for an example I guess. Suppose you are in a menu where option [E] selects the "Enter Message" function. Now, if you want to write a private message to the Sysop, using "Test" as a subject, you could enter: ESysop;Test;Y E "Enter Message" Sysop "Write message to" prompt ; Enter Test "Subject" prompt ; Enter Y Answer to "Private [Y/N]" prompt If you don't like to use command stacking all the time, but want to use it occasionally, you can enter a ';' at any menu prompt, and you will be able to enter a "command stack". - 122 - ┌──────────────────────────────────────────────────────────────────┐ │ The MORE prompt │ └──────────────────────────────────────────────────────────────────┘ If text is about to scroll off the screen, ProBoard asks the user if he/she would like to continue (if enabled). The user can enter 3 keys: [Y] to continue reading, [N] to stop reading or [C] to continue reading without further prompting. ┌──────────────────────────────────────────────────────────────────┐ │ The [S] & [P] key │ └──────────────────────────────────────────────────────────────────┘ You can stop almost any incoming text with the [S] key, and pause with [P] key. To resume a paused text, press [P] again or press the <Enter> key. The Sysop can disable this though. ┌──────────────────────────────────────────────────────────────────┐ │ Standard Chatting Procedure │ └──────────────────────────────────────────────────────────────────┘ New Sysops may not be familiar with online "chatting". There is one important thing you should know. It makes life much easier for you and the person you're chatting with. If you expect a response from the other side after you typed something, you should hit <Enter> twice to insert a blank line. This way the person on the other side knows you are done. - 123 - ╒══════════════════════════════════════════════════════════════════╕ │░░░░░░░ SOFTWARE DEVELOPMENT KIT ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════════╛ Included with ProBoard is the ProBoard Software Development Kit (SDK). The SDK allows C and C++ programmers to write extensions to ProBoard. The ProBoard Software Development Kit is bundled with ProBoard as free software. This means that you may use it to write extensions for ProBoard without having to register ProBoard. The only exception of course, is if you are using ProBoard to run a BBS on a regular basis. The extensions you can write for ProBoard are called "PEX" (ProBoard Executable) files. You may distribute any ProBoard PEX files you write royalty free. Just what exactly can a ProBoard Executable (PEX) file do? To illustrate what a PEX file is, we have bundled the shareware version of a PEX file called "EFL" (Enhanced File List) for your enjoyment and use. EFL is intended to enhance the normal file listing ProBoard displays when calling Menu Function 31 (List Files). Please refer to the next chapter "Enhanced File List (EFL) PEX File" for more information on installing and using this sample PEX file. Any PEX files you create with the SDK are run from within ProBoard using Menu Function 60 (Run ProBoard SDK file). For more information on using the ProBoard Software Development Kit (SDK) and the functions that it contains, please refer to the file included with this release of ProBoard, called "PB121SDK.DOC". - 124 - ╒══════════════════════════════════════════════════════════════════╕ │░░░░░░░ ENHANCED FILE LIST (EFL) PEX FILE ░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════════╛ The Enhanced File List PEX file provides ProBoard 1.21 with the ability to list and tag files. EFL was designed to give the Sysop complete control over the color regions of the file list, word-wrap, tag character, and more. A configuration utility (EFLCFG.EXE) is provided to setup EFL very quickly. ┌──────────────────────────────────────────────────────────────────┐ │ EFL 1.21 Installation │ └──────────────────────────────────────────────────────────────────┘ Follow these simple installation steps: 1. Put EFL.PEX, EFLCFG.EXE, and EFL.CFG into your PEX (C:\PB\PEX) subdirectory. 2. Run EFLCFG.EXE and choose the color combination and options you want. If you have monochrome, edit the EFL.CFG file with your favorite ascii editor (the file is well commented). 3. Install a line in your file menu and use Menu Function 60, run ProBoard SDK file. 4. Put "EFL" in the data field. Example: ──────── 0 1 2 1234567890123456789012345... <^F^>ile List via EFL Hotkey : F Function : 60 - Run ProBoard SDK File Data : EFL Level : 1 Flags : -------------------------------- - 125 - Color : White on Black Example Text 5. Examine your time/download limits in PROCFG. The security level field for every user level, should have a corresponding security level defined. This is standard practice. EFL won't allow users to download if their user level doesn't have a security level defined in PROCFG. The only exception to this rule is the Sysop. 6. If you are using FrontDoor and have a high-speed modem, please read the special FrontDoor note below. That's it! ┌──────────────────────────────────────────────────────────────────┐ │ FrontDoor Notes - High Speed Modems Only │ └──────────────────────────────────────────────────────────────────┘ Read CAREFULLY ────────────── In the FDSETUP, under Modem -> Messages: change the 1200 line from "CONNECT 1200" to "CONNECT 1200/". Also make sure you add an errorlevel for 12000 in the FDSETUP, under Misc -> Errorlevels. Then in your BBS.BAT (or whatever you call it) file, add the necessary support for responding to that errorlevel. This way FrontDoor will support 12000 bps connects and pass them properly to ProBoard. This will allow FrontDoor to properly answer 12000 bps calls, which otherwise come in at CONNECT 1200. Of course, you will need the proper modem (like a USR Dual Standard) in order for users to connect at 12000 bps. - 126 -